Eight steps, each with something written at the end.
The same path for a small fix and a multi-branch rollout. The scope sets the timing.
Discovery
We look at how the business runs today: branches, workflows, systems, devices, and who does what. Then we agree what is worth building.
Output: a map of the operation and a build list.
Design
We write the scope: workflows, integrations, roles, data sources, and how we will measure it. Nothing outside the scope gets built.
Output: a scope document both sides sign.
Build
We build the flows, the assistant, the dashboards, the app screens, and the device links.
Output: a working build on staging.
Integrate
We connect the software, data, and hardware on staging first. Every connection is logged.
Output: a connected staging system with logs.
Test
We run the acceptance checks with real samples from your business.
Output: a signed acceptance checklist.
Deploy
We roll out branch by branch, as written in the scope. Your staff use the system while we watch the cutover.
Output: a live system on the agreed branches.
Monitor
We watch runs, backups, AI usage, and alerts. Failures go to the team named in the scope.
Output: monitoring reports per contract.
Handover
You get the docs, training, and a walkthrough. The workflows, documentation, and data stay with you.
Output: a handover pack and a trained team.
Time, input, and ownership.
How long does a project take?
The scope sets it. It depends on the branches, workflows, integrations, and rollout stages.
What do we need to prepare?
Sample questions and documents, one contact person, and access to the systems in scope.
What is not included?
Anything outside the signed scope. New workflows, branches, or systems get a separate scope.
Who owns the work?
You do. Tool subscriptions stay on your account.
Not sure? Send us a message at the contact page.
Start with the operation.
Describe how the work runs today. We will map it and write the scope.
