US$150 per requirement.

You pay for the size of your specification. You see every requirement and the total before you pay anything.

Sample scope: car wash packages sold online
RequirementPrice
R1Packages with a set number of washesUS$150
R2Buying online with up to two licence platesUS$150
R3Washes only for the listed carsUS$150
R4Each wash counts downUS$150
R5Washes expire when the period endsUS$150
R6The period starts at the first washUS$150
TotalUS$900

You approve the list and the total before any paid work starts.

Your total comes from your own requirement list.

Each requirement includes

  • Its worked examples, with sample names and concrete numbers
  • The pass/fail checks that cover it
  • Expert review of every line

Every project includes

  • One round of corrections
  • One delivery check when your developer delivers
  • The final specification, yours to share with any developer

What counts as one requirement

A requirement is one rule or behaviour your software must follow, written so a developer can build it and a check can test it. Its edge cases belong to it. Worked examples and checks are part of their requirement and are never counted on their own.

Counts as one

R6: The period starts at the first wash.

Included in R6

Its worked example, and check C3 for a first wash 15 days after buying.

Corrections and changes

Your corrections
After you read the reviewed specification, one round of corrections is included, for anything that does not say what you meant.
Included
Our mistakes
If the specification wrongly records something you told us, we correct it at no charge, before or after you approve it.
No charge
New or changed rules
A rule that is new, or that you change after approval, is a new requirement at US$150, added only with your approval.
US$150

Terms

Who sets the count
We propose the requirement list after our first conversation. You approve the list and the total before any paid work starts.
Payment
Half when you approve the scope. The other half when we deliver the reviewed specification, before your round of corrections.
Timing
Up to 10 requirements take five working days from the day you approve the scope. For more, we agree the timeline in the scope.
While we wait for you
The clock pauses while a decision only you can make is open.
What you receive
A specification document that you own and can share with any developer.
The delivery check
When your developer delivers, we run the agreed checks with you on the delivered software, using a test link or account they provide, and report what passes and what goes back. One delivery check is included. A further check after fixes is quoted before it starts.

Get your requirement list and total

Tell us about your idea, and we will propose the scope.

Discuss your project
Discuss your project