Bring us your spec. Get a fixed price.
We capture your business rules once, in a rulebook you can read. Your database, API, admin app and docs are all derived from it. That is why we can quote one number instead of a range — and why you pay nothing up front and nothing at all unless you like what we build.
How every fixed bid works
Five packages, $0 to $25k →Send your spec
A doc, a spreadsheet, a deck, or a page of notes. Whatever you already have.
We build the Rulebook
Every table, field, role and rule, written once in plain English and in a form a machine can read. You browse it before anything is compiled.
You look, then decide
Try your edge cases. Pick what to compile it into. Pay only if you like it — then the repository is yours.
Why quotes are ranges
Every software project
hits the same wall.
Business rules get encoded once, and then again, and again. Into the database, the API, the frontend, the docs. Each copy drifts. A rule changes and you spend a week hunting every place it lives. This is not a tooling problem. It is an architecture problem. There is no single place that owns the logic — and that unknown is exactly what every estimate you have ever been given was padding for.
Logic scattered across the stack
Business rules end up encoded separately in the database, the API, the frontend, and the validation layer. Each location becomes its own source of truth. There is no single place to change a rule.
Changes cost more every time
When a rule changes, you have to find every place it lives, understand the blast radius, and update them all consistently. Miss one and you have a silent bug. The cost per change grows with the codebase.
The model stops being the system
Without a living model, the system is what the code says it is. Each layer has its own version of the rules, written at different times, by different people. To understand the system, you excavate. Code is archaeology.
Watch
Where decisions usually go.
A short walkthrough of what happens to business logic today, and what changes when it lives in a rulebook instead.
Why we can fix the price
Nobody can fix-price
code they have to type.
So we do not type it. The rules go into the rulebook once, and the database, the API, the admin app, the documentation and the tests are derived from it by the same build every time. The variable that turns everyone else's quote into a range is not in ours.
One rulebook, many targets
Postgres, a React app, REST and GraphQL, Python, Go, C#, RuleSpeak®, Excel, OWL — each generated from the same rules, none of them hand-maintained.
See the ecosystem →Checked, not asserted
The generated targets are tested against each other for the same answers, and every derived value traces back through the graph to the rule that produced it.
See how it holds up →We tell you where it stops
There is a known class of rule a model like this provably cannot express on its own. We name it up front and hand it an explicit mechanism, instead of you discovering it in month five.
Read the conjecture →Including on this site: the packages and prices are not written into the page. They are generated from a rulebook — the same kind we would build for you.
Or build it yourself
Same toolchain.
Free to use.
Everything we build your project with is open source. If you would rather run it yourself, take it — build, prototype and ship without paying us anything. Commercial licenses are for companies running many projects at once, and for large organizations.
- 01
Add Effortless to Claude Code
Two commands install the Effortless skills.
- 02
Describe your app in one sentence
Claude writes the rules and builds a working app.
- 03
Change a rule
Say it in plain language. The whole app follows.
Training
Go faster with a training session.
The fee converts to credit.
Getting started on your own is free. Training is the fastest way to get it right: we walk your team through the methodology, hands-on with real tooling. Pick the depth that fits where you are.
Free
1 hour onboarding
Not sure yet? Spend an hour with us. We'll look at your project, tell you honestly whether Effortless is a fit, and help you get going.
2 hours
Introduction
Hands-on walkthrough of the methodology and toolchain on a real project. By the end, you know exactly how to apply it on your next engagement.
Fully converted into store creditSee details →2 sessions
Hands-On Workshop
Build a real system slice from scratch - schema design, modeling surface setup, first effortless build, consuming views in app code.
$1,000 converts to store creditSee details →5 sessions
Team Onboarding
A complete adoption engagement for your team. Covers the full Bootstrap + Effortless Loop cycle and ends with a working, production-ready system slice your team owns.
$2,500 converts to store creditSee details →Larger scope · Custom package
Deep Enablement
For bigger teams and multiple projects: the full , edge cases, schema evolution, and organization-wide adoption. Scoped up front as a fixed package with a clear finish line.
Online sessions for individuals and small teams. For onsite workshops, firm-wide enablement, or larger engagements, get in touch and we'll work out the right arrangement.
See it in your context
Send us your spec.
Pay only if you like it.
No deposit, no discovery invoice, no range with an asterisk. We build the working version, you look at it, and the repository is yours.