Groundwork by Nimbus Analytica

How Groundwork works

Ten business days, four phases, one person accountable.

Book a Groundwork call Read the sample package→

The ten days

Day ranges are our plan, not a promise for every project. The clock starts when we have your intake.

  1. 01 · Days 1 to 2Frame.We confirm the problem, the users, the limits and your budget range. We agree what a good outcome looks like.
  2. 02 · Days 3 to 5Research and decide.We look at 3 to 5 alternatives, cost each one and write the decision memo.
  3. 03 · Days 6 to 8Design and build.We write the requirements and the architecture, build the cost model and set up the working skeleton in your account.
  4. 04 · Days 9 to 10Package.We write the scope pack and the build quote, and prepare the readout.

Then we meet for the readout, and you have 30 days of questions by message.

What we need from you

  • 01Answers to a short intake form
  • 02One person who can make decisions
  • 03A cloud account you control. We work in AWS. Ask if you use another.
  • 04A few hours of your time across the 10 days, plus the readout

If the answer is "buy" or "don't build"

You still get every deliverable. The decision memo explains why. The cost model compares the options you should consider. If the answer is buy, the skeleton is a test setup of the recommended tool in your own account where the vendor allows it. If it does not, it is a clickable prototype of the changed workflow. If the answer is not to build, you get a one-page plan for what to do instead.

You pay the package fee and owe us nothing more.

Sample, fictional company

Sample package

This sample uses an invented company. It is not client work. [PLACEHOLDER: build the sample before launch]

The scenario. A 60-person distribution company pays for three tools to manage quotes and wonders if a custom system would be cheaper.

DeliverableWhat the sample shows
Decision memoThe recommendation, the alternatives we compared and where each figure came from
RequirementsA must, should and won't list, with user stories and tests for each
ArchitectureOne diagram, the stack choices with the reasons, the data model and an integration map
Cost and ownership modelThree build paths as ranges, running costs, maintenance, a 3-year total and a risk register
Skeleton or prototypeA short recording of the working skeleton. Recording coming soon.
Scope packA statement of work and acceptance criteria
Build quoteAn example fixed-price quote with a timeline
Read the sample package

Ready to talk?

Book a Groundwork call