Skip to content
FortuneTech

Services

What we build

Six lines of work. Each one links to the platforms in our portfolio that demonstrate it, so you can go and look rather than take our word for it.

Savings, investment and credit platforms

For SACCOs, investment clubs and savings groups, we build the systems members save into and borrow from: contributions in tiers, share and revenue ledgers, interest posting and reversal, dividends, drawdowns, statements, and a documented way out for a member who leaves.

Land, plot and property sales systems

A public catalogue that reads the same inventory the sales team works from, so a reserved or sold plot changes on the website at the moment it changes internally. Buyers then get what they actually need: a shortlist, site visits, a reservation that holds the plot and a deposit paid online. Ruhaama's platform adds instalment plans.

See it in: Land, plot and property sales systems

Property management, and software sold to many businesses

One product that many businesses sign up to and use separately. PangisaPro is the example: each landlord or agency gets its own account, plan, branches and records, staff only see the properties they are assigned to, and we run the whole platform from one console. If you want to sell a product to many organisations, rather than have one system built for yourself, this is how we build it.

See it in: Property management, and software sold to many businesses

Payments and messaging integration

Mobile money and card payments through Flutterwave on every platform that takes payments, with Pesapal and Stripe on the newer ones; SMS through Africa's Talking, and login codes by SMS. On our newer systems, a payment counts only once the provider confirms it, so nobody is credited for money that never arrived. Receipts are PDFs, and adding or switching a payment provider is a settings change, not a rebuild.

See it in: Payments and messaging integration

Member portals, back offices and mobile apps

Most of our work comes in pairs: the portal a member or customer logs into, and the back office your staff run the organisation from. We build both, and each staff member sees only what their role allows. We also build what matters after launch: messages to all members and reports, plus, on the newer systems, a record of who changed what, bulk CSV uploads and two-step login for staff.

See it in: Member portals, back offices and mobile apps

AI assistants grounded in your own content

REMY, our own AI assistant, is in development and shows how we think AI should work on a business website: it answers only from content you have approved, shows where each answer came from, says so when it does not know, and never acts on a visitor's behalf until they have confirmed the exact action.

See it in: AI assistants grounded in your own content

None of these quite fit?

Describe what the system has to do. If it is not work we should take, we will say so.