Commitments
Not the pitch.The contract.
Anyone can promise a date on a call. We put ours in the contract, with a fixed price and a penalty if we miss it. Here’s everything else we put in writing, in plain English.
The terms at a glance
Section
A plain-English summary. Your signed agreement and scope of work govern.
01The guarantee
What happens, contractually,if we miss the date?
Every build ships on the date in writing. If we miss it on our end, the build is free, we still finish it, and we wire you $5,000.
Scope of work · §10 · Build delivery commitment
If Techify misses the ship date written in this scope of work1 for reasons within its control2, the build is free of charge3, Techify completes it at no additional cost4, and Techify pays the client $5,0005.
Cameron Sullivan
Founder & CEO, Techify AI
Signed before the build starts
The clause, in plain English
01
The date
On “misses the ship date written in this scope of work”: One ship date, to the day, written into the scope you sign before the build starts.
02
On our end
On “for reasons within its control”: Not a wait on access, credentials or feedback from your side. The scope sets those windows, in writing.
03
Free
On “the build is free of charge”: A full refund of the build fee.
04
Finished
On “Techify completes it at no additional cost”: We still finish it, to the win conditions you signed. The price doesn’t move.
05
$5,000
On “Techify pays the client $5,000”: Wired to you, on top of the refund. Out of our pocket.
There's always risk. Here's how we carry it.
Why it exists
It forces us to scope honestly, build with margin and never overpromise. It's also why we cap how many builds we take on. Ten active engagements at a time, so the standard behind this page holds.
- Ours
- The scope, the engineering and the date. If a slip is on our end, the clause applies.
- Yours
- Access, credentials and feedback, inside the windows written into the scope. To hit the date, we need them on time.
- Nobody’s
- What your market does with it. What a system earns depends on execution and on a market no engineering firm controls. Anyone who guarantees you that is selling confidence they haven’t earned.
02The scope
Seven thingsin every scope.
Before anything is built, you get the scope in writing. We walk you through it, you change what you want, you sign. Then it’s locked.
Scope of work
Seven sections
- 01
Deliverables
What we hand over, item by item.
- 02
Architecture
What it runs on, and why. Your stack if you have one. Our defaults, defended in writing, if you don’t.
- 03
Phases
Each phase has its own win conditions and date, and is accepted before the next one starts.
- 04
Timeline
To the day. Its ship date is the one the guarantee holds us to.
- 05
Win conditions
What it must do to count as done. We test against them before you sign off.
- 06
What we need from you
Access, credentials and feedback, and when we need each one.
- 07
One fixed price
Priced on the outcome, not the hours. It doesn’t move if a delay is ours.
- Sign-off
You sign. Then it’s locked.
Acceptance
Unlimited revisions inside the agreed scope, until you accept.
Done means the win conditions you signed. We test against them and revise inside the scope at no extra cost, then you sign off. Work outside the scope gets its own scope, price and date.
How a build runs03How you pay
Phase by phase.Paid, then built.
One fixed price, written into the scope and split into phases. Each phase is paid up front, then built. A small build can be a single phase.
Every build
Phase by phase
- PaidPaid up frontPhase 1
- PaidPaid up frontPhase 2
- PaidPaid up frontPhase 3
The payment lands, we build that phase
Fixed
The price in your scope is the price. It doesn’t move if a delay is ours.
Credited
If you start with the diagnostic, its fee comes off the first phase.
Handed over
Final payment hands over everything: code, IP, accounts, docs, SOPs and training.
04What you own
Built on your accounts.Handed over in full.
You open the accounts on day 0: cloud, repo, hosting. We build on them, and nothing lives on ours. The model and hosting bills run on your accounts too, so nobody marks up your tokens.
On final payment
- Code
- IP
- Accounts
- Docs
- SOPs
- Training
The docs: architecture, workflow maps, API docs and video walkthroughs.
After launch
Two weeks of tuning
For two weeks after launch we stay on to tune it. Not a take-it-or-leave-it hand-off.
Then
Your call
Run it yourselves, or keep us on for the next phase, with its own scope and date.
“Our goal here isn’t for you to be dependent on us forever.”
05Security and compliance
Built to surviveyour security review.
Only architecture that would survive a compliance audit. Here’s what that means in the build, and exactly what we hold and what we don’t.
Row-level security at the database engine
Every query, every time. No exceptions.
01Every extracted value stored with its source
Document name, page and a short evidence snippet, so any answer can be audited.
02Versioned migrations with rollback
Every database change versioned, each with a script to undo it.
03Architecture decisions in writing
Decision records say what was chosen and why, so the next engineer can maintain it.
04Every model call traced
OpenTelemetry and Langfuse, with cost alarms and circuit breakers.
05Humans approve where it matters
No rule change ships without a person’s sign-off.
06
What we sign, and what we build to
We sign BAAs.
And we design to the controls below, in the architecture and in how data is handled. NDA first, if you need one.
Your requirements, in the scope.
Whatever your industry requires is written into the scope of work and built to, with a certified partner wherever a framework calls for one.
Built to these controls
Applied in architecture and data handling, documented in the handover. Not a third-party certification.
HIPAA
Health data
SOC 2-ready
Type II readiness
PCI DSS
Card data
GDPR
EU data protection
CCPA
California privacy
PIPEDA
Canadian privacy
TCPA
Calls and texts
FDCPA
Debt collection
FCRA
Tenant screening
Fair Housing
Protected classes
ESIGN & UETA
Electronic signatures
Two-party consent
Call recording
OWASP Top 10
Application security
OWASP LLM Top 10
AI application security
NIST AI RMF
AI risk management
EU AI Act
AI governance
WCAG 2.1 AA
Accessibility
06What we won’t do
We won’t bill by the hour.We won’t lock you in.We won’t build what doesn’t pay you back.
- 01
No hourly billing
Hourly billing sets our margin against your timeline, and nothing in the contract settles it. Scope creep becomes the model. We took ourselves out of that incentive: one fixed price, on the outcome.
- 02
No lock-in
Your accounts, your code, your keys. No “we hold the keys” arrangement. You can leave any time.
- 03
No build without the math
Only what pays back three to four times its cost gets built. If the honest answer is a smaller fix, or no AI at all, you hear it from us first.
Next · The Diagnostic
Start with two weeks.Then hold us to the date.
The diagnostic is the way in. Two weeks inside your business: we find the constraint costing you the most, put a number on it, and hand you a 90-day game plan to fix it. Every build that follows ships on the date in writing.
The Diagnostic · Two weeks · $5,000
Architecture, case studies and references
- About two hours of your time
- Replies within one business day