Skip to content
Discuss a project

How a custom software project starts: the workflow review, written scope and agreed price

Working with us · 4 min read · 27 Oct 2026

The short answer. It starts with a 30-minute workflow review. We map how your business runs today, then send a written scope, timeline and agreed price before any work begins, so the cost does not move under you.

Step 1: a workflow review

A 30-minute call where you walk us through how the business runs today, including the spreadsheets, chats and paper. We ask which steps repeat, where data is typed twice and what slows the team down.

Step 2: a written scope and a agreed price

After the call you receive a written scope, a timeline and a agreed price before any work starts. The scope says what is included and what is not, so there are no surprises later.

Step 3: build, with weekly demos

You work with the people building the product, not intermediaries. Progress shows up as working software you can use, so you see the product take shape instead of reading status reports.

Step 4: launch and support

We launch on your own server, hand over the know-how, and stay available for support and maintenance if you want it. The code and data are yours from day one.

How to prepare for the call

  • List the tools you use today and what each is for.
  • Note the five most repeated tasks in your week.
  • Bring a sample of a report or sheet your team depends on.
  • Think about what would change if that work ran on its own.

You do not need technical language. Describe the work the way your team would, and we will translate it.

By Brown Button · 27 Oct 2026

Ready to talk it through?

Book a 30-minute workflow review. We will map how your business runs today and suggest a clear first step.

Discuss a project