scoporaStart Your Discovery

How It Works

Four stages that put a clear, approved scope in place before any proposal is requested.

  1. 1

    Discover

    Explain your business problem and discuss your requirements with the AI discovery assistant.

    You start a private project and talk through your business, the problem and what you've tried. The assistant asks a few questions at a time and tells you if existing software might fit better.

  2. 2

    Specify

    Receive a detailed, professionally structured software specification.

    From your discovery we draft a 21-section specification — from executive summary to outstanding questions — marking every point as confirmed, an assumption or unresolved.

  3. 3

    Approve

    Review, edit and approve the specification before anything is shared.

    You read, revise and compare versions. When you're happy, you approve one exact version. Until then, nothing is shared with any developer.

  4. 4

    Decide

    Review any proposal received against your approved scope, then choose whether to proceed, wait or seek alternatives.

    After you approve, we seek suitable independent developer proposals on that same scope. The number depends on availability. A proposal received can be reviewed against scope, price, exclusions, timeline and support; if several arrive they can be compared against the same scope. You choose whether to proceed, wait while we look for another developer, or use your specification to seek alternatives, and contract directly with any developer you choose. If you accept a proposal and proceed, scopora's one-off 15% success fee (on the agreed initial development value, excluding GST) is payable by you, separate from the developer's price and disclosed before you commit.

How developer proposals are compared

Every proposal is measured against the same client-approved scope, using the same weighted checklist. Price is one factor, not the deciding one.

  • Scope fit (25%): does it cover what you approved, and say clearly what it leaves out?
  • Price and terms (20%): is the price clear, with its basis, payment terms and any ongoing costs?
  • Timeline and delivery (15%): are the milestones realistic and tied to the scope?
  • Team and experience (15%): has the developer delivered similar work?
  • Technical approach (10%): is the proposed design sound and suited to your needs?
  • Ownership, support and risk (10%): who owns the code and intellectual property, and what support follows launch?
  • Communication and fit (5%): how clearly and promptly the developer answers questions?

Watch for red flags: a quote that does not list its exclusions, no ongoing support figure, no written code and intellectual property terms, or a price not tied to the approved scope.

scopora helps you compare proposals. It does not manage delivery or guarantee the outcome.

Read our guide to writing a software requirement

Who is responsible for what

You own your specification. You contract directly with your chosen developer, who is responsible for delivery. scopora does not guarantee any developer's quality or delivery.

Start Your Discovery