Monitoring and backups
Uptime checks, nightly backups and restore drills. You get the monthly report, we carry the pager.
Report every monthHow we build · fixed price · twelve weeks
Twelve
weeks
from
brief
to
production
Our method is an instrument. It measures what your company already does, finds the centre, sets the direction, and builds outward in two-week sprints, at a price agreed before we start.
Scroll to explore
The instrument
A milestone ring, sixteen workstreams, forty-five checks
We plan a build the way an engineer reads a site: a ring marked for every working day, sixteen workstreams around it, thirty-two milestones on the outer ring, and forty-five checks in the grid, laid over your own operation.
1 The brief
Your business, to the outside face of the walls
Paid discovery, one to two weeks. We sit with every desk, open every sheet and group chat, trace the outline of how work actually moves, and measure each process the way you run it today.
2 The core
Find the centre
Every system has one point everything else is measured from: the record that must never be wrong. The order, the ledger, the employee file. We find it first and build outward from it.
3 The first journey
The door your team enters by
One workflow, end to end, chosen with you: the one your team runs ten times a day. It is designed, built and signed off before anything else, and it sets the axis for the rest of the build.
4 Fix the price
Scope agreed. Price locked.
With the brief and the first journey agreed, the quote is fixed. Thirty percent to start, forty at design sign-off, thirty at launch. No day rates and no change-order surprises; new work is quoted the same way.
5 Two-week sprints
Sixteen workstreams, one build
Every fortnight, a demo of working software by the engineer who wrote it. Each workstream rises to the effort it needs: pale where we configure, deep maroon where we build from scratch. Milestones light up as they close.
6 Quality
Forty-five checks, eighty-one cases
Automated tests over every workstream, and the grid above the centre is our release checklist: security, backups, performance, data migration. Nothing ships until the grid is complete.
Effort balance
Northline build · hours per fortnight · indicativePale, configuredDeep, built from scratchLines: (avg + max) / 2 · average · (avg + min) / 2
7 Launch and handover
Two pages, in your name
Page one is the handover sheet: repositories, servers, credentials and the architecture inside the ring. Page two carries the support plan and the runbook. The code, the servers and the data are yours from day one.
After launch
Then we keep it running
Launch is the door. Behind it: hosting, monitoring, updates and a team you can call, on one fixed monthly plan.
Fixes within the plan
Defects are fixed inside the plan, in the same week, not billed by the hour.
Same weekNew work, quoted
A new branch, a report, an integration: scoped and priced the same way as the first build.
Fixed priceTraining and handover
Your team trained, your IT handed the keys. Leave us any time and take everything with you.
Yours from day oneBegin
Ready to start your build?
Tell us what your team runs on today. The engineer who would build it calls you back, and you receive a fixed price within one working day of that call.
The team
Built in India, by people you can call.
Engineers, designers and the people who answer the phone. The person who demos your software is the person who wrote it.