Skip to main content
Reactll — AI & Software Engineering Reactor Technology

One written scope, one price that does not move.

Agreed before anyone writes code. A written list of what will be built, what will not, and one fixed price, with milestones and a start date. If we estimate badly, the overrun is ours, not yours.

Why a fixed price

Why one fixed price?

Payment is 40% to start, 30% at the midpoint and 30% on delivery. Two revision rounds are included. If we estimate badly, the overrun is ours.

These terms are published on our pricing page, not revealed in a contract at the end. The code sits in your own code account from day one.

Written scope. One price. Your code.

1

Fixed price, agreed before any code

40/30/30

Payment at start, midpoint and delivery

2

Revision rounds included in every build

2018

Building and running production software since

What we hear

Three sentences that usually come before a quote

01

“Every quote is a day rate and a guess.”

One fixed price for a written scope, with milestones and a start date. Running costs are listed separately. It is a number you can put in the budget, and it moves only if you change the scope.

02

“Our last project was nearly done for four months.”

Every item in the scope gets a plain-language check for when it counts as done. At the midpoint you get a working piece of the system. Done is judged against the document. If the work takes us longer, that is our cost.

03

“We know what to build. We need it written down and priced.”

We write the features as things a user or admin can do. We list what is left out and what you provide. You correct anything we misunderstood before a price is set.

What you get

A scope you can compare line by line, not just a total

01

Written Scope

Features written as things a user or admin can do, plus the screens and steps. It also lists the systems it connects to, such as Stripe, PayPal or iyzico, your WooCommerce store or an accounting tool.

02

Out-of-Scope List

What this price leaves out on purpose. This part explains why two quotes differ, and most quotes skip it.

03

Assumptions and Inputs

Copy, images, product data, account access, test cards and store developer accounts, each with who provides it and when.

04

Price, Milestones and Changes

One number split 40 / 30 / 30, a delivery date and two revision rounds. A new screen or rule is a scope change, priced first. Running costs for outside services are listed separately.

Who it is for

A fixed price is fair when the scope can be written down

If the first version can be written down, we take the risk of a wrong estimate. If it cannot yet, a fixed price only moves the argument to the end.

A good fit

  1. 01

    You know what needs building, or the audit or roadmap has decided it, and want a price you can commit to.

  2. 02

    You need a fixed number for a budget, an investor or a board, and a written definition of done.

  3. 03

    You want to compare our quote fairly against others, line by line.

Not a fit yet

  • The First Version Is Still Vague

    A fixed price on a vague scope only moves the argument to the end.

    Build one working part first, or start with Discovery

  • You Want Hours, Not a Build

    Developers by the hour, or a two-year programme with a steering committee.

    A Run plan with monthly hours, or a larger firm

How a quote is made

From what is known to a signed price

  1. Step 01

    Start From What Is Known

    A Discovery call, a System review report or a roadmap step, or a scoping conversation if none exist.

  2. Step 02

    Write the Scope

    You correct anything we misunderstood here, where corrections cost nothing.

  3. Step 03

    Price It

    One fixed price against the written scope, with milestones, running costs and a start date.

  4. Step 04

    Sign, Then Build

    Work starts on the first payment. The code lives in your own accounts from day one. Ownership of the work (the IP) passes to you as each payment is made.

FAQ

Questions people ask before a quote

Every build gets one fixed price, agreed against a written scope before any code. The price depends on the number of user roles, the systems it connects to, any old data to move over, and whether there is a mobile app. Typical ranges are on our pricing page.
Fixed price, when the scope can be written down. You know the cost before you commit, and we pay for any overrun. When the work cannot be defined yet, build one part first or use a monthly plan. Do not force a number onto guesswork.
They include different things. Compare what each quote leaves out, not only the totals. A cheap quote often quietly stops at admin screens, email templates, password reset, error pages, moving old data and privacy pages.
40% to start, 30% at the midpoint and 30% on delivery, invoiced in EUR, USD or GBP by Reaktör Teknoloji Tic. Ltd. Şti. For early teams, the same total can be spread monthly across the build.

Want a written scope and one price before any code?

Tell us what needs building. We agree what is in, what is out and the price before work starts.

Book a Call 30 Minutes