Tell us what you need built

Describe the software you need and Brennan Builds will come back with a written scope and a price. No account, no payment, no obligation.

What happens next

  1. 1. You describe the software below. It takes about ten minutes if you already know what it must do.
  2. 2. We read it and decide honestly whether it is something we can build well. If it is not, we say so and point you at the nearest thing we can.
  3. 3. If it is, you get a written scope and a fixed price — including what is not included, and what we would need from you.
  4. 4. Nothing is built and nothing is charged until you have read that estimate and approved it.
*

How the work gets done today, and what is wrong with that. Concrete beats polished — the spreadsheet everyone is emailing around is a better answer than a mission statement.

*

The people who open it, roughly how many, and how technical they are. This decides how much of the software can assume and how much it has to explain.

*

A range, not a commitment. It tells us which version of this is worth scoping — we would rather quote something you can say yes to.

*

If a date is fixed by something outside your control, say so in the problem above.

What the software must do

These questions are about the application itself — not about how it looks. They are what we build from, so the more concrete you are here, the closer the first version lands.

*

The kinds of record the software stores. One row each — these become the screens and tables your team works in.

*

Each kind of person who logs in, and what that kind of person is allowed to do. One row per role, not per person.

*

The jobs someone opens the software to get done, start to finish. Walk each one through in the order it actually happens.

Third-party services the software has to read from or write to. Leave this empty if it stands alone.

Anything the build waits on that only you can provide — accounts, API keys, a data export, a sign-off. Naming them now is what stops the build stalling later.

Getting in

Above you listed what you would give us. This is the harder question, and the one that decides whether a price is worth writing: for each system or set of records, can anyone actually let us in, and how soon? Nothing here widens what we take on — it stops us quoting around a door that turns out to be locked.

*

Accounts, systems, spreadsheets, a database, records that already exist somewhere. Answer this even if the answer is no — "no" is an answer we can quote against.

One row each. Leave it empty if this stands alone. If you are not sure whether something counts, add it — an item we did not need costs a sentence, one nobody mentioned costs weeks.

Where to send the scope

We reply to you directly. No account, no mailing list.

*
*

Where the scope and the price go. We do not add you to anything.

Sending this costs nothing and commits you to nothing.