Engagements
How working with us actually works.
How a scope becomes a number, what a week looks like from your side, what happens when something changes, and how it ends. The commercial mechanics, written down before you ask.
- Week 1
- Written scope, no code
- Fixed
- The number does not move
- Friday
- Working software, weekly
- 30 days
- Notice, both directions
Three ways in
Most people start at one of these.
01
Start with a week of thinking
When you know the problem but not the shape of the solution. One to two weeks produces a written specification, a fixed quote and a delivery date. You keep the document whether or not you continue, and it comes off the project price if you do.
Product DiscoveryFixed engagement02
Build it to a fixed number
The main engagement. Week one is scope, weeks two and three are build with a Friday demo on your real data, week four is deployment, training and handover. The price is agreed before anything starts and does not move.
Web ApplicationsFixed-price project03
Keep it running afterwards
Monitoring, monthly patching, incident response and a steady pace of improvements, from the engineers who wrote it. Rolling monthly with thirty days' notice, and thirty days of fixes are included with every build regardless.
Managed SupportMonthly retainerThose are the common routes. All twelve services sit across 5 groups, and most engagements combine two or three of them under one scope and one number.
Pricing mechanics
How a scope becomes a number.
Fixed price only works if the scope is written down first. That is the entire reason week one exists, and the reason we will not quote from a conversation alone.
Week 1
Week 2
Week 3
Week 4
01
A call
Thirty minutes. What is going wrong today, who it affects, and what you have already tried. You leave knowing whether this is a conversation worth continuing.
02
Week one
Access, a walkthrough of how the work actually happens, and a written specification: screens, rules, edge cases, and what is out of scope.
03
One number
Quoted against that document, with a delivery date. It is comparable against any other firm's quote because they would be quoting the same spec.
04
It holds
The number does not move. If you change the scope we re-quote the difference in writing first, and you decide.
Both directions
What each side signs up for.
The projects that go badly are almost never technical. They are the ones where nobody on the client side could make a decision without a meeting.
What we commit to
- A fixed number quoted against a written scope, which does not move
- The engineer who scoped it is the engineer who builds it
- Working software every Friday, on your real data
- The repository in your organisation from the first commit
- Thirty days of post-launch fixes at no extra cost
- An honest assessment when we are the wrong firm for the job
What we need from you
- Around three hours a week: a demo and a handful of decisions
- One named person who can decide without convening a committee
- Access to the systems we are integrating with, early
- Reading the specification properly before signing it
- Telling us when something has changed on your side
Boundaries
Things we will not do.
Bill by the hour
It rewards the party doing the estimating for being wrong. Fixed price puts that risk where it belongs.
Take equity instead of payment
It sounds appealing to both sides and it aligns nobody. Better to be a supplier you can fire.
Hold your code hostage
The repository is yours from the first commit, including if you walk away halfway through.
Quote a project we cannot deliver
If it is bigger than we can do well, or outside what we know, you hear that on the first call.
- How does a scope become a fixed number?
- Week one. We watch how the work happens today, get access to your systems, and write a specification covering screens, rules, edge cases and what is explicitly out of scope. You sign it, and the quote is made against that document. No code is written until it is agreed, because that is the cheapest week in which to change your mind.
- What happens if we want to change something mid-build?
- We re-quote the difference in writing before touching it, and you approve it or you do not. Nothing gets silently absorbed and presented as a surprise at the end. Small clarifications that do not change the work are just done — we are not going to invoice you for a re-worded label.
- What if you underestimate the work?
- That is our problem, not yours. Fixed price means the risk of a bad estimate sits with the party who claimed to be able to estimate. It is also why week one exists and why we will not quote from a conversation alone.
- How do you invoice?
- Projects are split across the engagement rather than billed entirely up front, with the schedule written into the agreement. Retainers are monthly in advance. There are no hourly line items to reconcile, because there are no hours being counted.
- What does the Friday demo actually involve?
- About an hour. You click a real thing with your real data in it and tell us what is wrong. It is not a slide, a screenshot or a percentage. The point is that problems surface in week two rather than in week four.
- How does an engagement end?
- With handover as a deliverable rather than a conversation: the repository, infrastructure accounts, documentation written for people rather than engineers, and two recorded training sessions. Retainers end on thirty days' notice with the same handover, written into the agreement from the start.
- What if it is not working out?
- Say so early. For a project, you keep everything built to that point and the specification. For a retainer, thirty days' notice and a handover session. We would rather end something cleanly than manage a relationship nobody is enjoying.
Start with the thirty-minute call.
You’ll leave it with a number and a date, whether or not you end up working with us.
Phone
+1 (407) 796-2376Reply time
One business day, from an engineer
Based in
Orlando, Florida · serving the United States
What happens next
- A reply within one business day, from an engineer
- A thirty-minute call, with no qualifying call before it
- A written scope and a fixed number, if it fits