One system. Nothing missing. Yours.
Most businesses run on WhatsApp threads, spreadsheets, and guesswork. RP fixes that. Whatever your business does, we build and run the system it runs on — end to end, from the first customer call to the final payment.
- Site supervisorDaily plan opened for DAR-07. Four crew assigned.06:50
- CrewArrival confirmed on site. GPS position logged.07:14
- FitterMaterial request raised against the task waiting on it.REQ-0118
- AdminPurchase order issued against the project budget.PO-0093
- CustomerOpened their portal. Sees progress on their project only.PORTAL
- AdminInvoice raised from the job record. TZS, 18% VAT, TIN on the PDF.INV-0041
- The systemJournal entries posted. Receivable, revenue, VAT payable. Balanced.AUTO
Seven people · nobody retyped anything — worked example
No re-typing between tools. No lost paperwork. One record, from the call to the ledger.
- Projects & sites
- Daily plans
- Photo check-ins
- GPS field map
- HSE toolbox talks
- Quotes → invoices
- 18% VAT
- TIN & VRN on every PDF
- Purchase orders
- Project budgets
- Material catalogue
- Reorder alerts
- Double-entry books
- Trial balance
- AR ageing
- In-app chat
- Live notifications
- Demand forecasting
- Churn prediction
- RFM segmentation
- Customer portal
- Audit log
The problem
One job. Six places. No single version of the truth.
Nothing here is broken software. It is the absence of software. Every piece of a live job sits somewhere different, and the only thing joining them is somebody’s memory and a phone call.
It works, right up until the day it does not: the quote nobody can find, the crew nobody can account for, the invoice raised twice, the margin discovered a month after the job closed.
A WhatsApp group
The customer’s original request
Someone’s notebook
What was agreed on site
An Excel file
The quote — version 4, probably
A paper site report
Who actually worked, and when
A printed delivery note
What materials went out
The accountant’s inbox
The books, six weeks behind
The alternative
Or somebody else’s system, rented by the head.
There is proper software out there. It was designed for businesses in other countries, and it is sold the same way everywhere: a catalogue of modules, a licence per person per month, and an implementation partner to close the distance between what it assumes and where you actually trade.
It works. It is also how a company of twelve ends up paying for software built for a company of twelve hundred, and training its people to speak the software’s language instead of the other way round.
A catalogue of modules
You will open six of them. You pay for all of them.
Per seat, per month
A bill that grows with your headcount, in a currency that is not yours.
A localisation project
Consultant hours spent teaching it that Shillings, an 18% VAT rate, and a TIN exist.
Their vocabulary
Your people learn the software’s words for the work. The software never learns yours.
The system
Everything goes in one place. Everything comes back out of it.
There is no integration layer, because there is nothing to integrate. The field report, the quote, the purchase order, and the journal entry are all rows in the same database — the one deployed for your business and nobody else’s.
Customer request
Type, description, the project it belongs to. Logged the moment it arrives.
Site & scope
Site code, milestones, budget. One project can carry many sites.
Field report
Daily plan, arrival timestamp, status photo, GPS position, toolbox talk.
Material request
Raised against the exact task that is waiting on it.
One database
Your own deployment. Your logo on every document. Nobody else’s data in it.
Quote → invoice
Branded PDF, TZS, 18% VAT, TIN and bank details already on it.
Purchase order
Drawn against the project budget, allocated versus spent, visible live.
Journal entry
Double-entry, posted automatically from the invoice. Debits equal credits.
Analytics
Momentum, forecast, churn risk, and a ranked list of what to do next.
The paperwork
A tax invoice that looks like it came from here.
Not a foreign template with the currency symbol swapped. Tanzania Shillings, an 18% VAT default matching the Mainland standard rate, the customer’s TIN, your VRN, and your bank instructions — on the PDF, automatically, every time.
- Numbering
- Sequential, year-stamped, generated atomically. Never a duplicate and never a gap you have to explain to an auditor.
- Totals
- Subtotal, tax, and discount are calculated on the server and never trusted from the browser, so a quote cannot be edited in transit.
- Posting
- Finalise it and the books move: receivable, revenue by service line, VAT payable. Posting it twice never double-counts.
NYUMBANI CONTRACTORS LTD
TIN 123-456-789 · VRN 40-123456-A P.O. Box 7841, Dar es Salaam
NCL-INV-0042 Issued 14 Jul 2026 · Due 28 Jul 2026
BILL TO
Kimara Properties Ltd · TIN 987-654-321 Site KIM-04 · Project PROJ-DAR-07-2026
PAYMENT
CRDB Bank PLC · A/C 0150 4491 7700 Quote NCL-INV-0042 as the payment reference.
The field
The work happens on site, so the system lives there.
Office software asks people to file paperwork after the fact. This is built the other way round: the crew opens the day with a plan and closes it with a report, from the site, on a phone.
- Daily plan, daily report
Custom report forms per site, and arrival confirmed with a timestamp.
- Photo check-in
A status photo attached to the report — proof of presence and progress on a low-bandwidth connection.
- GPS positions
Latitude, longitude, address, and status, feeding a live map built on OpenStreetMap. No paid maps key.
- HSE toolbox talks
Topic, attendees, duration, and notes, logged against the site for compliance and audit.
- MWZ-02
- ARU-05
- DOM-01
- MOR-03
- DAR-07
- ZNZ-01
- MBY-04
- MWZ-02
- Mwanza
- Fibre backbone
- ARU-05
- Arusha
- CCTV & access control
- DOM-01
- Dodoma
- Substation civils
- MOR-03
- Morogoro
- Warehouse supply
- DAR-07
- Dar es Salaam
- 4 on site · reporting
- ZNZ-01
- Zanzibar
- Hotel electrical
- MBY-04
- Mbeya
- Tower maintenance
- Built-in roles
- 6Built-in rolesEach with its own dashboard
- Service lines
- 4Service linesSeparate reporting, out of the box
- Analytics pipelines
- 2Analytics pipelinesNo BI subscription
- Shared databases
- 0Shared databasesYour deployment is yours
Where it is proven
Proven in four trades. Built for whatever yours is.
Quote an electrical job on Monday and a fibre installation on Tuesday: both land in the same system and report separately, out of one chart of accounts. That is where the platform was hardened — not where it stops.
Telecom & ICT
Fibre runs, towers, network installs. Crews across regions, materials against tasks.
Security systems
CCTV, access control, alarms. Site surveys, commissioning, service history.
Electrical & civil
Substations, wiring, groundworks. Toolbox talks and HSE records that hold up.
Building supply
Stock, reorder levels, delivery notes. Retail analytics on your own sales data.
Why RP
What makes RP different.
Built for you, not at you.
Imported software makes you adapt to it. RP adapts to your business — your workflows, your terminology, your words on the screen.
A build, not a licence per head.
You are not renting seats in somebody else’s product. The system is built for your business and it stays yours as the team grows.
We build it. We maintain it.
Most tech firms build and disappear. RP stays — maintaining, evolving, and supporting your system as the business changes.
Proven end-to-end, today.
Not a roadmap. Not a prototype. The platform your deployment starts from is built, deployed, and running — from quote to cash, working now.
Not a template with the currency swapped out.
Shillings, TIN and VRN fields, 18% VAT, CRDB payment instructions, site codes, toolbox talks. Built from how the work runs here, then generalised — not imported and patched.