Skip to content
GrowmoonGrowmoon
WhatsApp LinkedIn

How to scope a software project and compare proposals

Use this guide to define one outcome for your first software release. Give every bidder the same workflow, exclusions and acceptance checks so you can compare what each proposal will deliver.

Illustration: two proposal documents on a balance scale with a magnifying glass beside them

Start with one outcome

Name one task a user needs to complete. For a weekly spreadsheet approval, record who submits the request, who reviews it and what happens next. Include a typical request and an exception so each bidder can estimate the same work.

Define the first release

List essential workflows separately from useful later improvements. For each essential workflow, describe its input, expected result and acceptance check. State which browsers or devices matter, the roles people need and any accessibility requirements. Keep a decision log so later changes can be assessed against the agreed scope.

Distinguish discovery from a build commitment

Turn one approval into a decision card

Before accepting an estimate for an internal tool, write one example that the buyer and engineer can both inspect. An approval workflow is useful because it exposes rules that a page mockup can hide.

The following card is invented for planning. It describes a requested behavior, not an implemented Growmoon product.

Turn one approval into a decision card
DecisionExample to agree during discovery
RequestA staff member asks to purchase one item and supplies a reason and amount.
ActorsA requester submits; an assigned reviewer decides; an administrator manages assignments.
PermissionThe requester cannot approve their own request. Decide who may reassign a reviewer.
Accepted recordThe stored decision identifies the request version, reviewer, decision and time.
Repeated actionA repeated approval refers to the existing decision. Conflicting decisions need an explicit rule.
AmendmentChanging the amount after review creates a new version and requires the agreed review step.
ExceptionAn absent reviewer leaves a visible pending item with a named escalation owner.

Ask the engineer to identify which rules can use an existing product and which require new work. Keep unresolved points beside the card. A diagram showing the intended roles helps scope discussion; acceptance needs evidence from the chosen implementation.

Separate the outputs you are buying

Discovery and implementation answer different purchasing questions. Put their deliverables in separate proposal lines so that a discovery result can be assessed before it becomes a build commitment.

Separate the outputs you are buying
Proposal lineUseful deliverableBuyer acceptance
Workflow discoveryVersioned actor map, sample inputs, permission rules and exceptionsThe operational owner confirms that the important decisions and exceptions are represented.
Technical assessmentExisting-product fit, system dependencies and open feasibility questionsAn accountable engineer identifies evidence behind the proposed approach and unresolved dependencies.
Build optionBounded requirements, exclusions, acceptance cases and estimate assumptionsBuyer and engineer agree which outcomes the estimate covers.
ImplementationThe agreed source, configuration and behavior in an authorized test environmentA separate reviewer checks the specified successful and failed journeys.
Handover and careAccount ownership, operating instructions, incident route and support boundaryThe nominated operator can find the evidence and follow the agreed recovery procedure.

Record the people who approve scope changes and the effect on fees or timing. For a remote engagement in the US, UK or Australia, agree review overlap and escalation arrangements with the actual participants. The buyer's country alone does not establish working hours or an available local team.

Bring the decision card, one permitted sample and a list of open dependencies to a scope discussion. Leave credentials and private employee records out of the initial enquiry. The existing proposal comparison guide supplies the broader ownership and cost checklist; this card supplies a more precise approval example.

List the systems the software must connect

List the systems the product will read from or write to. Record who controls access, whether a sandbox exists, rate limits and expected failure behavior. An integration that works only with an ideal response is incomplete. Include retries, duplicate handling, mapping rules and what a user sees when a dependency is unavailable.

Compare the same deliverables

Ask each proposal to identify included design work, development, migration, testing, release preparation and handover. Separate third-party subscriptions, hosting, licenses and optional support. A low headline price may cover a smaller scope; a higher price may include work you do not need. Compare the written deliverables rather than the headline alone.

Clarify ownership and operations

Confirm source-code delivery, third-party licenses and who will own the cloud, domain, repository and store accounts. Agree the documentation needed to run the system. Discuss backups, monitoring, operational access and what happens when the original developer is unavailable. Do not leave these decisions until handover.

Agree how you will accept the first release

For an approval workflow, a useful check is whether a user without the required role is prevented from approving a request. For an integration, test a timeout and a repeated event as well as a successful response. Write down who performs acceptance, how feedback is recorded and what counts as a scope change.

Questions to take into a proposal review

Which assumptions could change the estimate? What must we provide? Which dependencies could delay release? What is excluded? How are defects distinguished from new features? What support remains after handover? Keep the answers next to the proposal so the commercial comparison stays grounded.

A short brief you can reuse

Include: the business problem; users and roles; three essential workflows; existing systems; data involved; target devices; dependencies; desired timing; budget context; and the acceptance criteria. A clear brief reduces ambiguity, but a fixed price or date still depends on the agreed scope.

Choose between adapting a product and building from scratch

Start with the workflow you need and evidence from the actual product version. A catalogue starting point can reduce the amount of new work only when the included behavior, licence and architecture fit your requirements. A custom build also needs clear scope and acceptance criteria; neither route removes integration, testing or operating costs.

Questions to compare an existing product with a custom build
DecisionExisting product or templateCustom build
Workflow fitDemonstrate the exact included journey. List every change required.Describe the journey and agree an acceptance example before implementation.
Rights and accessVerify the licence permits the planned use and modification; confirm source and backend access.Agree ownership and deliverables, including any third-party components.
Integration effortCheck the selected version against provider APIs, access requirements and data formats.Define API contracts and failure behavior as part of the scope.
Release effortIdentify installation, branding, migration, store submission and compatibility work still needed.Identify these same tasks alongside design and development.
Ongoing responsibilityClarify vendor updates, custom-change compatibility and maintenance ownership.Clarify maintenance, dependency updates, monitoring and handover.

Compare all project and operating costs

Ask for separate lines for discovery, interface work, implementation, integrations, data migration, testing, deployment and support. Hosting, store accounts, content rights and provider subscriptions may be recurring costs. The development entry range on our working-arrangements page is a discussion threshold, not an estimate for every item in this table.

Download a brief you can complete privately

Use the worksheet below to record requirements and unanswered questions before a call. It includes prompts for every Growmoon service and for catalogue customization. Leave confidential data and credentials out; a completed worksheet is a starting brief, not a contract or fixed quote.

Download the project brief worksheet (.txt) · Download the proposal comparison sheet (.csv)

Discuss your project brief

Share the workflow, product or integration you have in mind. We will use the brief to discuss scope and a sensible next step.

Start a project conversation