The spec is the test

Custom software, delivered with proof.

qtide is one platform from written requirements to proven software. Plan the work, let agents build against specs you approve, and test every change with AI. Run it yourself, or have us run it for you.

Runs healthcare and telecom systems. Prefer it done for you? Our engineers deliver on it at a fixed price.
spec 4.2 / conformancepassing
Specification
A refund request over $500 must be approved by a second reviewer before it is issued.
approved · v3 · 12 Aug
Conformance check
refund.dual_approval
over_threshold
single_reviewer blocked
audit_entry_written
ran 4 min ago · commit 9f2c1ab
94% of spec statements covered

Everyone can generate code now. Almost nobody can prove it's right.

Custom software has always failed in the same place: the gap between what you asked for and what got built. You write requirements. Someone interprets them. Months later, the demo shows what got lost, and fixing it is expensive by then.

AI made that worse, not better. Teams ship more code with less review than ever, and nothing connects the code back to the ask. So the only question that matters goes unanswered:

Does the software match what we agreed?
How it works

From your requirements to a running system, on one thread.

Everything in qtide runs the same loop. Nothing is handed off, retyped, or lost between tools.

01
Specify
Your intent becomes a written spec. You read it, change it, approve it. Nothing gets built until you do.
02
Plan
The approved spec breaks into components and milestones, so every task traces back to what asked for it.
03
Build
Agents generate the system against the spec. Your engineers, or ours, direct, review, and correct it.
04
Run
Every change deploys to a live environment you can use, not a slide deck.
05
Prove
The spec compiles into tests that run on every change. When something drifts, it fails loud and says where.
That last step is the one nobody else does. It's why the rest can be trusted.
The platform

One platform runs every step.

The loop above is not a process diagram. It is software we built. Specs, planning, build agents, testing, environments: one system, one thread of data from the ask to the verdict.

Start with one piece or run all of it. Every tier below works on the same thread of data, and you own everything it produces.

01 · SPECIFY
Specs that compile.
Versioned, approved, and compiled into tests. When a spec statement changes, the tests that enforce it regenerate with it.
02 · PLAN
Product management on the thread.
Milestones, tickets, and traceability from every task back to the spec statement that asked for it. No second tool to keep honest.
03 · BUILD
Agents that build to the brief.
Scoped to the folders they may touch, capped in spend and steps, and never merged without a verdict. Directed by our engineers.
04 · RUN
A live environment for every change.
Every change deploys somewhere you can click, isolated from everything else. The demo is never the first time you see it.
05 · PROVE
Test cases that trace.
Every test maps to a spec statement. Coverage means statements proven, not lines executed, so 94% covered means something.
05 · PROVE
Testing that never lies.
Recorded suites run on every change. AI-generated tests probe what the recorded ones miss. A check that could not run fails. It never silently passes.
Your own agents, if you want them.OPTIONAL

Most teams use ours. Some define their own, per project: which folders an agent may touch, what done means for it, and what it may never do. Same limits, same verdicts, defined from your project settings.

/Scope is the blast radius
/Spend and step caps you set
/Watch in plan mode before you trust it
One thread of data runs through all six. That's what makes the verdict trustworthy, and the price fixed.
Why qtide

Why this holds up when other builds don't

The spec is the contract.
You approve a written spec before we write any code. Scope stops being a memory argument.
The spec is the test.
Prose specs rot silently. Ours compile into tests, so a spec that's drifted fails out loud.
You see it running from week one.
A live environment, updated on every change, yours for the whole build.
Variance is engineered out.
The same process runs on every project. That's how we quote a fixed price and hold it.
You own the outcome.
Code, spec, tests, infrastructure. No proprietary runtime, no lock-in.
Who it's for

For delivery owners, and the engineers who live with it.

Delivery owners and project managers

Head of engineering, product owner, founder: if the result is on you, you need one thread from requirement to release, and certainty that what ships is what was agreed.

/Delivery you can verify, not just review
/Fixed scope and fixed price
/A spec your stakeholders can read and sign
/Engineers you can actually reach
/Your team stays on what only they can build
Your engineering team

The people who live in it every day. Whether your team builds on qtide or inherits what our engineers deliver, everything is built to be read, tested, and owned.

/A real spec, not a two-line ticket
/Tests built from intent, not from the code they check
/An isolated environment per branch
/Conventional code in your stack
/Full handover: repo, docs, tests, infrastructure
Pricing

Start where it hurts. Grow into the factory.

Three tiers, one platform. Upgrading is a switch, not a migration.

Projects
Per usermonthly
Project management, built on living specs.
/Specs generated from your requirements
/Versioned, approved, enforced
/Every ticket traces to a spec statement
/One place for requirements and work
/Standups, and a client view for stakeholders
Best for: requirements and tickets that live in different worlds.
Start a conversation
Testing
Per usermonthly
Everything in Projects, plus proof.
/Test cases tied to spec statements
/Automated and AI testing on every change
/Verdicts that fail loud, never silently
Best for: teams shipping faster than they can verify.
Start a conversation
THE COMPLETE FACTORY
Factory
Per projectmonthly
Everything, together. This is qtide.
/Everything in Testing
/Agents build against approved specs
/A live environment per change
/Your own agents, scoped and capped
Best for: approved requirements in, proven software out.
Start a conversation
Delivered for you.FIXED PRICE

Our engineers deliver your project on the Factory: a two-week Specification Sprint, then a full build at a fixed price. You own everything at handover.

Talk to us
Questions

The ones that actually come up

Tell us what you're trying to build.

The first conversation is about your problem, not our platform. If it's a fit, next is a Specification Sprint: two weeks, fixed price, and you keep it either way.

We reply within one business day. We don't add you to a mailing list.