About us
The work is rarely the problem. The record is.
Projects seldom fail on workmanship. They fail on administration - a bill nobody kept current, a budget nobody could read, and a client who found out too late to act.
Our story
It started with a build we could not verify.
Our founders tried to put up a building while living somewhere else. It went the way it usually goes: updates when somebody remembered, costs that moved without a paper trail, and no way to check anything without asking a favour.
So we went and asked. Hundreds of conversations with contractors and homeowners produced the same account from both sides: competent people, honest work, and no shared record capable of proving either.
SiteBooks is the system we wanted to exist: one record both parties can open, kept current from site as the work happens. When the evidence is shared, trust stops being something anyone has to extend on faith.
How we work
Four positions we hold.
Evidence over assurance
Every claim about a job should be backed by something dated and checkable. We design for disclosure, and we do not ship features that make it easier to obscure.
The phone is the computer
Construction happens on site, on a handset, on an unreliable connection. If a feature does not survive those conditions, it is not finished.
Local rails, global users
Mobile money, bank transfer and card, in your own currency and your own working hours. Usable from any timezone a client happens to be in.
Trade language, plainly used
We use the words the industry uses, correctly. What we do not do is invent new jargon, or dress a simple idea up to look sophisticated.
The team
Small, hands-on, and usually on a site.
Builders, engineers and operators, some on site and some working remotely. We take support calls ourselves, which is the fastest way to meet us.