Custom business software, built around how you already work
In most companies, the dozen things the team does every day live in spreadsheets, WhatsApp threads and one person’s memory. Another platform to adapt to will not change that.
What it is
An internal suite is written in your vocabulary, prints your documents and enforces your permissions. Those are the three things off-the-shelf software makes you work around.
We design against one failure in particular: the same fact living in two places. It is the most expensive bug we know, and it never looks like a bug. A price that lives in the contract and again in the operations screen will drift, and one day a villa is billed at double. It has happened to us, and it is why every tool we build reads a single source for each fact, and why adding a tool never means copying a list.
Client portals and third-party integrations are on this sheet rather than on their own, because in practice they are not separate products: the portal is the same data with a different door, and the integrations are what stop your team retyping it.
Seen working
Lawang Estate — thirty-two tools, one system
A property developer runs sales, contracts, invoicing, construction, commissions and banking in one intranet. Thirty-two tools under one menu and one login, with roles per person: an agent sees their own buyers, a manager sees their team, finance sees the money. Every price is read from the document that sets it, and every buyer exists in exactly one place.
- tools under one menu
- 32
- login for the whole team
- 1
- figures typed twice
- 0
How it flows
- STEP 1LeadArrives in the CRM with its source.
- STEP 2ReservationThe plot is held, with a deadline.
- STEP 3ContractGenerated from the record, signed remotely.
- STEP 4InvoiceIssued from the contract, receipt attached.
- STEP 5BankThe statement line is matched to the receipt.
- STEP 6AccountsEvery project knows what came in and what is owed.
What's included
| # | COMPONENT | WHAT IT MEANS |
|---|---|---|
| 01 | Data model | One source per fact. Prices, dates and names are written once and read everywhere. |
| 02 | Documents | Contracts, invoices and receipts generated as PDF from the record itself, so nobody types them twice. |
| 03 | Roles & permissions | Per user and per tool. What someone cannot do, they cannot see. |
| 04 | Client portal | A door for the people outside the company, on the same data, with its own rules. |
| 05 | Integrations | Payments, calendars, spreadsheets and messaging, wherever the data already lives. |
| 06 | Languages | The interface in as many languages as the team speaks. |
| 07 | Handover | Source code, database and deployment. Written so the next developer can read it. |
Questions
Is this an ERP?
Sometimes it replaces one, more often it sits beside one. An off-the-shelf ERP is good at what every company does the same way (accounting, payroll). It is bad at the part that makes you different, and that part is usually where the money and the mistakes are. We build that part.
We already use spreadsheets and they work. Why change?
Spreadsheets work until two people edit them, until a number has to appear in a document, or until someone leaves. The time to change is when somebody starts retyping the same data.
Can you build on top of what we already have?
Yes, and it is usually cheaper. If the data already lives in a system with an API, we read it rather than migrate it.
How long does it take?
It depends on scope, so we do not quote a number before understanding yours. Tell us what the team does today and we come back with scope and a price.
Who can use it? Only the office?
Whoever you give a role to. In the case above the developer’s team, the construction side and the buyers all use the same system through different doors.
Have something worth building well?
Tell us what you are working on. We usually reply within a day.