Software engineering · AI world

Human judgment and AI,
working as they should.

Loopwright is software engineering for the modern AI world. People own the decisions — scope, what "done" means, what ships. AI does the labor inside those lines. Nothing ships until a real acceptance suite is green and a person approves it. Quality and economics, held together.

Acceptance suite as the authoritative build gate
Per-build cost report — billed tokens, dollars, tiering
Three human gates · nothing ships without approval
Claude + Vercel today · portable by design

What you get

Built different, accounted for honestly

Not a promise of speed or magic — a documented process where quality and cost are tracked together and every build is verifiable.

🏛️

You own the decisions

Scope, acceptance criteria, and what ships are human calls at three explicit gates. AI works inside the lines you draw — never around them.

🔬

The suite is the gate

Acceptance criteria are frozen before a line of code is written. A build only moves forward when the full suite is green. No green, no ship — full stop.

📊

Economics on every build

Every build prints a real cost report: billed tokens, dollars, which features stayed on the fast tier and which escalated, and what tiering saved. It shows nothing rather than inventing a number.

🔄

Outcomes, not hours

You specify what "done" means. We deliver that or we don't ship. The contract is the acceptance suite — not an hours estimate.

🔌

Portable by design

Model-agnostic agents, swappable model tiers, build backend behind one interface. Claude is today's engine. Vercel is today's deploy target. Both are plain facts, not lock-in.

🐕

We eat our own cooking

Loopwright's own products are built on the same engine, suites, and gates we offer you. If something is broken or slow, we feel it first.

The process

People decide. AI builds.

Three human gates. AI doing the labor inside the lines. A frozen acceptance suite as the only build oracle.

1
Human gate · Scope

You define done

You describe the product and what "done" means. Together we turn that into an acceptance suite — concrete, testable criteria. Nothing starts until you sign off.

Gate: scope approved
2
Build — suite-gated

AI works inside the lines

The suite is frozen. Building runs iteratively until every criterion is green. The economics report accumulates in real time — tokens, dollars, tiering decisions.

Gate: suite green
3
Human gate · Ship

You approve the diff

You review the build, the passing suite, and the economics report. Nothing deploys on autopilot. Your approval is the final gate.

Gate: release approved

Quality and economics — one mandate, not a trade-off

Every build produces a real economics report. Billed tokens and dollars. Which features held on the fast tier and which escalated to a more capable model. What tiering saved.

If a number can't be verified, it doesn't appear. That's the whole model: under-claim, then show the receipts.

// build economics · example output
build id lw-2024-0619-a3f1
acceptance suite 24 / 24 green

tokens billed (total) 1,243,800
↳ fast tier 1,101,200
↳ escalated 142,600

build cost $0.34
tiering saved ~$1.20 vs all-capable
model engine claude (today)
deploy target vercel (today)
🐕

We build on it ourselves

Loopwright's own products — including this site — are built on the same engine, suites, and gates we offer you. Same acceptance criteria. Same economics reports. Same three human gates. If the process has a rough edge, we find it before you do.

Ready to build something real?

Tell us what you're building and what "done" means. We'll turn that into an acceptance suite, run the build, and bring you the diff and the receipts.

Onboard your product