From first call to running system.
Nothing gets built off a phone call. Here is what happens, in order, and what you hold at the end of each stage.
01
Thirty minutes, by phone
Intro Call
A diagnostic conversation, not a pitch. We establish what the current process costs, and whether that justifies building a system around it.
What we ask
Walk us through an ordinary day, and we follow the points where it breaks. What is held on paper, in a spreadsheet, or in one person’s memory. What you have already tried, and why it did not hold.
What you receive
An honest answer on whether there is a problem worth solving
02
Working sessions on site and remote, delivered in five to seven business days
Workflow Assessment
The part nobody else does at this size. We document the operation as it runs, not as it is described.
Observation
We record how work moves through the operation. Shifts, handoffs, queues, and the points where a job stalls or doubles back.
Leadership interviews
We interview leadership for the top-down view. How the process is meant to run, and what it costs when it does not.
Ground-level interviews
We interview the people who execute the process for the bottom-up view. The two accounts rarely match, and the difference is where the cost sits.
Gap validation
We return with specific questions, chase the edge cases, and watch a handoff end to end.
Synthesis
Offsite. We draft the process map and the module list, then two remote calls to close open questions.
What you receive
A written assessment of the operation as it runs today
The inefficiencies we found, and what they cost
The system we propose, in plain language
A fixed price and a timeline
03
Three to ten weeks depending on scope, followed by a consolidated revisions round
Build
Development follows the module list from the assessment. Where a change is warranted, it is documented and priced before any work begins.
How you stay informed
A written report on the same day each week: what is done, what is in development, and any movement in scope or schedule. No standing meetings.
The revisions round
The working system enters a review window, five business days for a single module and ten for a larger build. You send one consolidated list, worked through in a single round.
What counts as a revision
A revision adjusts what was built. It does not add what was never scoped. Anything outside the module list is a change order, quoted separately.
Launch
Two training sessions, one for management and one for daily users, plus handover documentation. Defects in the first thirty days are fixed at no charge. Code and data ownership transfers on final payment.
What you receive
Working software in production
Two training sessions
Handover documentation
Thirty days of post-launch bug fixes
04
Ongoing, with a twelve month initial term and sixty days notice
Partnership
When a fault surfaces mid-week, the person fixing it should be the person who designed it, not a support tier reading a ticket cold.
What is included
Infrastructure, uptime monitoring, daily backups, security patching and defect resolution. Support is answered the next business day, and the engagement carries eight development hours a month.
Quarterly workflow review
Each quarter we review what the system does against what the operation now needs. Businesses change faster than the software built for them.
What you receive
Hosting, monitoring, backups, security patches and bug fixes
Eight development hours a month
The in-app Support tab
A quarterly workflow review
Support lives inside the software, not in a separate portal.
Every application we deliver has a Support tab built into it. You do not log in somewhere else and you do not email a shared inbox and hope.
A bug, a change, a question, or a new feature. It becomes a ticket the moment you send it.
Captures who was logged in, what page they were on, and what they last did. You do not have to reproduce anything.
Every request you have sent, its status, and how it was resolved. Nothing gets lost in an email thread.
Straight to our calendar when something needs a conversation instead of a ticket.
It begins with a conversation.
A thirty minute conversation to establish what the current process costs and whether a system is warranted. You will leave with a clear answer in either direction.