How we work
A clear path from discovery to delivery.
Fixed scope before any build starts. Working software you test before it ships. Full handover of code, intellectual property and documentation at delivery.
Process
How an engagement moves forward
- 01
Discovery
A discovery call, and it is about the work rather than the software. What the process actually is, where the time goes, which systems hold the data, what the workarounds are, and what a fix would be worth. We ask about the spreadsheet somebody maintains, because that is usually where the real rules live. A mutual NDA is signed before project details are shared.
In this step- Discovery call covering the operation rather than a feature list
- Mutual NDA signed before details are exchanged
- An honest answer about whether custom software is the right call
- 02
Architecture
A technical call with engineers, then the specification. We document the workflows, the data model, the integrations, the access rules and the edge cases. The output is a written scope you confirm. It is fixed before development begins. New findings or requested changes are discussed with you before changing the agreed work.
In this step- Technical call covering systems, interfaces, data and constraints
- Written specification with screens, rules and integrations
- Fixed scope agreed in writing before the build begins
- 03
Build
A dedicated project manager runs the cadence and a team lead is accountable for the technical decisions. You see working software at each stage rather than progress reports. The schema comes first because it outlives every interface drawn on top of it, then the application, then the integrations, each with its retry and failure handling designed rather than added later.
In this step- Dedicated project manager and a team lead with industry experience
- Working software at each stage, not status documents
- Changes to scope are written decisions with their impact stated
- 04
Integration and validation
Your team uses it against the specification, on real work, before anything ships. Quality assurance runs in parallel against the ranked risk list: the rules that carry money, time and access. Defects are logged against the specification so there is no argument about whether something is a bug or a change.
In this step- Acceptance testing by your team against the written specification
- Quality assurance against the ranked risk list
- Defects tracked against the specification rather than against opinion
- 05
Launch and handover
Deployment and full handover: source code, intellectual property assignment, documentation, credentials and a deployment guide. Recovery procedures are documented where the delivered system needs them, according to the agreed scope. After delivery you can maintain the product yourself, hand it to another team, or discuss a tailored support plan.
In this step- Deployment into infrastructure and accounts registered to you
- Handover of source code, IP assignment, documentation and credentials
- Runbook covering deploy, rollback, restore and incident response
- 06
Iteration
Use operational feedback to decide the next change. Improvements are scoped and reviewed before implementation. Post-delivery support plans are available, use a ticketing process and are tailored during discovery or technical discussions.
In this step- Review operational feedback and integration exceptions
- Agree the scope of subsequent product changes
- Tailored post-delivery support through a ticketing process
Coverage
Time zones and calls
We work with clients in North America and Europe, and the overlap window for your engagement is agreed before it starts.
| Discovery call | About the operation rather than the software. Held under a mutual NDA. |
|---|---|
| Technical call | With engineers. Covers systems, available interfaces, data and constraints. |
| Markets | North America and Europe |
| Overlap window | Agreed per engagement before work starts |
| Support languages | English, French, Spanish and Filipino |
| Contact | The quote form or support@sawhorsesoftware.tech |
Handover
What you receive at delivery
This is the part that makes the rest meaningful. You own it outright, and you are free to take it anywhere.
| Source code | The complete codebase in a repository you control |
|---|---|
| Intellectual property | Full assignment of the IP in everything built for you |
| Documentation | Architecture, schema, operating procedures and known constraints |
| Credentials | Every account and key, held in accounts registered to you |
| Deployment guide | Written for someone who was not on the project |
| Runbook | Deploy, rollback, restore, key rotation and incident response |
| Tests | The automated suite, fixtures and continuous integration configuration |
Let’s talk about the system you need.
Tell us where the current process breaks down. We can map the workflow, examine the integration requirements and define a practical scope for the build.
- A mutual NDA is signed before project details are shared.
- Scope is fixed in writing before any build starts.
- You own the source code, the IP and the documentation at delivery.
- Support plans are available and tailored on a discovery or technical call.