Solidus Private

Home / Resources

Resources

What a written build plan should cover.

Published 15 November 2026 by Solidus Private

A tablet showing a four-step plan timeline on a walnut desk

Before you pay anyone to build software for your business, get the plan on paper. These are the eight things a good plan answers. If one is missing, ask for it before you sign.

1. What gets built

Each part named in plain words, such as answering inquiries, quoting, customer records, scheduling, invoicing and AI agents, and what each part does on a normal day.

2. What it replaces

Every subscription and manual step it takes over, by name, with what you pay for each today.

3. What stays

The tools you keep and how the new system connects to them, so nobody types the same data twice.

4. Where the data lives

Which services hold your information, whose name the accounts are in, and who can see what.

5. What waits for a person

Which tasks agents handle on their own and which wait for approval, such as anything sent to a customer or anything involving money.

6. The price

In writing, for exactly the scope in the plan, before you commit to anything.

7. The handover

Documentation, training for your team, and how the builder's access is removed when the work is done.

8. After launch

What ongoing help is on offer, and a plain statement that none of it is required to keep what was built.

If a plan can't say what it replaces or whose name the accounts are in, you are being asked to rent something new, not to own it.

How Solidus handles it

Every Solidus build starts with this plan. It follows a 30-minute strategy call, it comes with the price in writing, and we start building only after you approve it. Book a strategy call to get one for your business.

See what your own stack would look like.

On a 30-minute call we go through what you pay for today, and the written plan shows what a system in your name would replace.