Home / How We Work
ProcessNothing is configured before the workflow is understood. Nothing goes live before your team has used it. And every step ends with something written down that you can keep — because a step that doesn’t produce a document isn’t finished, and isn’t billed.
We sit with you — on campus, in your office, or on a call, whatever is easy. We map how things work today, where it hurts, and what “fixed” should look like. You leave with a one-page discovery note and an honest list of your top three problems.
We configure the system with your own words on the screens — “follow up”, “closed”, “enquiry” — and show you a working copy as it grows. Nothing is hidden, nothing is finalized behind your back, and every configuration decision is written down with its reasoning.
Your data is migrated, counted and reconciled — with an exception log for anything unusual. Your staff run the system in rehearsal with us beside them. Then it goes live on a day you choose, with a signed go-live checklist.
From that day, we watch: updates, fixes, tested backups, follow-ups. You get one short note every month — what ran, what changed, what we recommend next. The system stops being a project and becomes part of the furniture. That’s the point.
Every step ends with a written artefact your management can review. If a phase doesn’t produce one, it is not complete — and it is not billed.
How your office works today, in plain language. Data formats sampled, pain points ranked, and the top three problems agreed with the people who run the place — not read from a form.
A live instance with your terminology and module list, plus a written scope: what we’ll build, in what order, over how long, at what effort. Both yours to keep, both readable without us.
The system running on your data. Alongside it: row-count reconciliation, the exception log, the signed go-live checklist, and records of who was trained, and on what.
Tickets opened and closed, patches applied, backups restored and verified, and one or two recommendations for the coming period. Short enough to read over chai, complete enough to file.
Four rules we don’t bend, whatever the timeline.
One named engineer owns your file from start to steady state. Escalations never restart the story from scratch — the person who knows the system is the person who answers.
Scope, access changes and data operations are confirmed in writing first. A live system never moves on a verbal instruction — protects you and protects us.
Launches and heavy changes are scheduled around exams, festivals and busy season — never in the middle of them. We plan the month around you, not the other way.
Hosting, domain, data and credentials stay in your name. We work under access you grant, every credential we hold is logged, and a clean handover is always possible.
Tell us in two or three lines how your office works and what hurts. We’ll reply with an agenda for a 30-minute call — same working day.