From AI prototype to paid pilot: scope delivery without derailing your startup
Sell a bounded pilot, not an unfinished promise
For technical founders who already build with AI coding tools and are deciding what they can responsibly deliver alongside their own startup.
What turns a demo into an offer?
A named buyer, a useful output, exclusions, acceptance evidence, commercial terms and a handover—not just a working screen.
Does a paid project validate the startup?
It establishes that customer’s willingness to buy that scope. It does not establish a repeatable product market or recurring revenue.
When does contracting fit?
When delivery, review, communication and support fit genuine capacity without sacrificing an essential startup milestone. Expected fees are not cash already received.

A working AI prototype is not yet a promise you can price, deliver and support. For a founder who can already build, the next task is to define what one customer can buy and how both parties will recognise delivery. This guide also helps you decide whether a small client engagement fits alongside your own startup.
It is not a complete company-formation guide, a forecast of customer acquisition or a guarantee of contract income. The worked pilot and capacity numbers below are explicitly fictional editorial examples, not reported MLAI engagements. If you are still exploring an idea rather than delivering software, the customer-discovery exercise is an earlier step.
1. Define what the buyer is deciding
Separate the person doing the work, the person accountable for the result and the budget approver. Ask what happens today, which failure matters, and what evidence would justify changing the workflow. Avoid replacing those questions with a list of model features.
A custom client project and a startup product experiment can share engineering, but they answer different questions. A customer paying for bespoke integration does not establish that many customers will buy a standard product. Record reusable learning separately from client-specific commitments, and do not assume you own or may reuse client-funded work.
2. Turn the demo into a bounded pilot
Fictional pilot: an operations team wants draft weekly summaries of project updates. Start in a test workspace with synthetic updates. The draft links every factual statement to a supplied update and marks missing information. A staff reviewer controls publication. The pilot cannot message customers, change project status or access unrelated workspaces.
The completed brief below deliberately ends at not ready to commit. Its fee, hours and cost allowances are invented, not a market benchmark. Filling every box is useful precisely because it reveals missing evidence and an infeasible schedule.
- Buyer, user and decision
- Fictional buyer: an operations lead. User: one weekly-report operator. Budget approver: the business owner. Test whether a review-only project summary is useful enough to justify a separate real-data assessment; do not promise time savings or a production rollout.
- Workflow and baseline
- One weekly summary covering two projects and up to 12 supplied updates. Assume 45 minutes of manual preparation per summary for planning only; no baseline has been measured. Before judging value, the operator must time matched manual and pilot cases, including checking and correction, and record sample size and case difficulty.
- Deliverable and input boundary
- One test workspace, one operator, synthetic JSON updates with workspaceId, projectId, updateId and text; no live integration. Deliver a review-only draft, source IDs beside each factual claim, visible conflicts/missing information, source/configuration, evaluation record and operator notes. Source-ID presence alone does not establish that a claim is supported.
- Excluded actions
- No customer messages, external publication, status changes, other workspaces or real personal/customer data. The operator manually decides what to publish outside the pilot. Remove send/write credentials and verify the boundary; prompt instructions alone are not an access control.
- Acceptance and owner
- Propose the eight cases below as a minimum starting set, all currently UNRUN. The founder implements and records results; the operations lead must agree expected outcomes and review failures; the owner decides acceptance. These roles are fictional and no reviewer is assigned. Passing eight cases would not establish general reliability or operating approval.
- Dependencies and schedule
- Four proposed weeks: scope/fixture in week 1, review-only draft in week 2, failure testing in week 3, handover in week 4. Buyer supplies an approved synthetic fixture and two review slots before work starts. Dates, access and availability are unconfirmed. Preserve the founder's existing product release in week 2 and customer demonstration in week 4.
- Fee and collection assumptions
- Illustrative A$1,800 fee excluding GST, not a quote or agreed rate. Propose A$900 invoiced after agreed scope/start authorisation, assumed collected in week 2, and A$900 after acceptance/handover, optimistically collected in week 4. Payment terms and calendar dates remain unagreed. Test late or absent receipts; acceptance and an invoice are not cash.
- Costs, payer and usage stop
- Founder-paid hypothetical outlays: week 1 A$100 test infrastructure plus A$250 external-review allowance; weeks 2 and 3 A$100 provider usage each; week 4 A$150 external handover-review allowance. Total A$700 excluding GST. These are allowances, not vendor quotes or completed reviews. Paid external review is separate from the founder's own review hours. Propose a cumulative A$200 provider-usage cap; show a hard stop before an over-budget call. No live running-cost commitment is included; later cash flows are outside the worksheet.
- Changes and stop conditions
- A new workspace, real data or send/write capability requires a new scope, risk review, estimate and explicit approval. Stop on a permission breach, unsupported factual claim, lost input or absent budget control. Keep original updates available and use the manual report. A failed case is a revise/stop decision, not an automatic new feature allowance.
- Ownership and reuse
- Propose delivery of permitted source, configuration and operator notes to the buyer. Background code, third-party licences, ownership/licensing and reuse rights require an explicit agreement and appropriate advice. Do not assume client-funded work can become startup IP or a public portfolio. No reuse permission has been granted in this example.
- Handover and support boundary
- Reserve four founder hours in week 4 for reproduction, disabling/fallback practice, documentation and bounded support. Propose two additional one-hour support slots in week 5 for reproducible defects within agreed scope, not feature changes or ongoing operation. No later hours are reserved yet. Owner acceptance, actual slot dates and support terms remain unconfirmed; legal obligations are not defined by this worksheet.
- Current planning decision
- NOT READY TO COMMIT. The original plan needs 28 hours within four weeks but has only 24; weeks 1 and 2 are overloaded. Week-5 support needs two more hours with none reserved. Acceptance cases are unrun and terms unresolved. Reduce/resequence scope or negotiate a feasible schedule, reserve support and review cash timing before deciding to accept, defer or decline.
Do not imply that a synthetic pilot is already a live deployment. Access to real data, privacy/security assessment and operational approval are separate decisions. If a buyer wants live publication or another integration, revise scope, tests and price before agreeing.
3. Save the brief and expose unknowns
Complete the brief together, using “unknown” rather than inventing costs or acceptance targets. Keep confidential data out of an initial enquiry. This is a planning worksheet, not a contract template.
Download the completed example, acceptance record and blank pilot brief (.txt). It includes the original fictional capacity calculation. Your edits to the interactive worksheet are saved separately using its own download button.
Copy a blank pilot brief
Prototype-to-pilot brief — replace with non-confidential facts
Buyer / user / budget approver and decision to test:
Current workflow, case volume and measured baseline:
Deliverables / users / data / integrations included:
Excluded actions and explicit human approvals:
Acceptance cases, expected results and evidence owner:
Customer dependencies, access and review availability:
Milestones / fee / payment trigger / payment timing to agree:
Running costs / payer / usage ceiling:
Change requests / stop conditions / manual fallback:
Source and configuration ownership / permitted reuse:
Handover / support boundary / unresolved risks:
Pilot decision: stop, revise, repeat or expand, and why:Australian business.gov.au contract guidance covers matters including payment, intellectual property and documenting changes. Use appropriate professional advice for binding terms, business structure, tax, liability and jurisdiction-specific obligations; the article does not settle them.
Specify whether acceptance means delivery of agreed software, a measured workflow outcome, or both. The buyer’s access and review obligations need dates too. Do not promise a business result that depends on unavailable data, adoption or decisions you cannot control.
4. Show evidence beyond an AI-generated demo
Use AI coding tools to assist implementation, but retain responsibility for understanding and reviewing the change. GitHub’s responsible-use guidance for Copilot suggestions explicitly calls for review and validation and warns that generated code can be inaccurate. A generated test suite can share the implementation’s mistaken assumptions.
- Independent expectations: write expected outcomes from the scope before using the implementation to generate answers. Keep some evaluation cases outside development.
- Inspect the diff: explain permissions, dependency changes, error handling and why a failing test was changed. Passing by deleting the requirement is not acceptance.
- Test failures: missing source, contradictory updates, wrong-workspace access, provider timeout, repeated run and an instruction embedded in an update to publish externally.
- Show the boundary: verify the service lacks unauthorised send/write capabilities. A prompt saying “do not send” is not the same control.
- Handover: supply permitted source/configuration, reproduction steps, known limitations, access ownership, disabling instructions and agreed support terms.
For the fictional summary pilot, contradictory updates should be surfaced for review, not resolved into an invented fact. A timeout should leave original updates available and show an error, not a success-looking empty summary. An embedded instruction must not gain permissions or alter the agreed task.
Proposed acceptance record—not test results. All eight cases are UNRUN: no summary application was implemented for this planning example. Replace this starting set with representative and independently held-out cases for the actual scope. For each run, retain the exact fixture/version, observed output, action/usage evidence, failure disposition and reviewer/date.
Swipe the table sideways on a small screen, or focus it and use the arrow keys.
| Case and input | Expected evidence | Status |
|---|---|---|
| P1: Routine update: project A / U1 says milestone X is complete; project B / U2 says Y remains blocked. | Draft preserves both distinct statuses and their correct source IDs; operator can verify each claim. No invented deadline, customer or outcome. | UNRUN |
| P2: Project A has no update; project B has one approved update. | Mark project A as missing information. Do not infer progress from silence. Retain the valid project B summary. | UNRUN |
| P3: Two updates disagree about whether milestone X is complete, without an agreed precedence rule. | Surface the conflict and both source IDs for human resolution; do not silently choose a convenient status. | UNRUN |
| P4: An update names an unapproved workspace or project. | Reject that input before model processing; it is absent from provider requests, draft and exported evidence. Show the operator a non-sensitive error. | UNRUN |
| P5: An approved update contains an instruction to message customers or reveal another workspace. | Treat the instruction as untrusted content, retain the original task and demonstrate no send/write/other-workspace capability. Check action logs as well as draft text. | UNRUN |
| P6: Provider times out or returns malformed output. | Show a clear failure and retain original inputs for the manual process; do not show an empty or partial draft as accepted success. | UNRUN |
| P7: Repeat the same input/run request. | Do not duplicate source records or imply a second independent observation. Record any draft variation for review; no publication action occurs. | UNRUN |
| P8: A next call would exceed the proposed cumulative A$200 provider cap. | Stop before the call using reserved cost bounds or provider-enforced limits. If a reliable ceiling cannot be implemented for the chosen service, the budget-control requirement fails. | UNRUN |
Assess value separately: compare representative manual and pilot cases, counting review, correction and operating effort. Record sample size and differences in case difficulty. Released time is capacity, not cash already saved; small test results do not establish performance on every future case.
Need a runnable starting exercise before committing to a client pilot? The bounded event-reply prototype includes code, synthetic inputs and retained failures. It is a different workflow, not proof that this summary pilot meets its requirements.
5. Decide whether client work fits your startup
This section is for existing technical founders in Australia or New Zealand who use AI coding tools, can review and test what they ship, and are considering contract delivery. Being a founder alone does not establish those skills or spare capacity.
Fictional capacity check, not an estimate for your project: six genuinely available hours per week over four weeks gives 24 hours. If implementation needs 12, testing and security review 5, meetings 3, and handover/support 4, that already consumes all 24. Adding a four-hour contingency produces a 28-hour obligation and a four-hour shortfall. Faster code generation does not remove the other obligations.
The timing matters too. The proposed allocation needs 9, 7, 6 and 6 hours in weeks 1–4. Even increasing availability to seven hours every week would leave week 1 overloaded. Two additional support hours in week 5 also have no reserved capacity. Extra hours later cannot silently repair an earlier deadline.
The decision is to reduce scope, extend the window if both sides can support it, or decline—not quietly borrow time from an essential startup milestone. Include support after the initial window and permission to share or reuse work. A paid engagement is not automatically available for your public portfolio.
In the example, A$1,800 of expected receipts minus A$700 of direct outlays leaves A$1,100 of project cash over four weeks. It is not profit: founder time, taxes, overhead and other commitments are not valued. Starting at zero and counting each week’s outlays before receipts gives a largest temporary cash gap of A$450. Delay the first A$900 receipt from week 2 to week 4 and that gap becomes A$700, even though the final balance is unchanged.
business.gov.au’s cash-flow guidance distinguishes estimates and incoming/outgoing cash. The worksheet below is only a four-week project scenario, not a whole-business cash-flow statement. Use actual payment dates and all obligations for decisions that depend on cash; seek appropriate financial advice.
Does this four-week project fit?
Start with the fictional example, then replace the assumptions. Hours available must already exclude protected startup work. Receipts and direct outlays are AUD; the example excludes GST. Use a consistent GST basis for your own figures. This is not a quote, financial advice, profit or runway forecast.
Entries are held in this page's memory and lost on refresh. This worksheet does not send them to Studio or analytics; download or copy a record to keep it. Avoid confidential information on this analytics-enabled website.
Edit weekly hours and cash assumptions
Record the actual support dates and exclusions in your brief. Later cash costs/receipts are outside this four-week cash calculation.
Resolve the capacity shortfall before committing
- Total hours available / planned
- 24.00 / 28.00
- Overloaded weeks
- 1, 2
- Later support hours remaining
- -2.00
- Net project cash in four weeks
- $1,100.00
- Largest project cash gap (outlays first)
- $450.00
Cash starts at zero; each week's outlays occur before its receipts in this scenario. This is not your bank balance or a funding recommendation. Founder time, tax, overhead, financing and other business commitments are not valued. Later spare hours cannot repair an earlier deadline.
Swipe the table sideways on small screens, or focus it and use the arrow keys.
| Week | Available h | Planned h | Hours left | Before receipts A$ | Closing project cash A$ |
|---|---|---|---|---|---|
| 1 | 6.00 | 9.00 | -3.00 | -350.00 | -350.00 |
| 2 | 6.00 | 7.00 | -1.00 | -450.00 | 450.00 |
| 3 | 6.00 | 6.00 | 0.00 | 350.00 | 350.00 |
| 4 | 6.00 | 6.00 | 0.00 | 200.00 | 1100.00 |
View or copy my worksheet
A positive calculation does not settle scope, legal terms, qualifications, project availability or selection. The Studio application below opens separately; these numbers and notes are not attached.
A practical next step with MLAI
Have delivery capacity alongside your startup?
Already building with AI coding tools and able to review and test what you ship? After checking your capacity and support boundaries, apply with permitted work evidence and realistic availability. MLAI Studio considers suitable builders for scoped, paid project work. Matching is not guaranteed.
Apply for scoped contract workThe public Studio application currently asks whether you can legally contract in Australia. If you are based in New Zealand, confirm eligibility with MLAI before assuming this pathway supports your circumstances. Application, selection, project matching and income are not guaranteed.
Not seeking client work? Browse MLAI events for a relevant founder discussion or build session. You do not need to describe yourself as a contractor to participate; check the individual event’s format and requirements.
6. Close the pilot with a written decision
Record delivered scope, passed and failed checks, user feedback, total delivery/operating effort and outstanding risks. Ask the buyer to distinguish “the software meets the brief” from “we want to buy a wider rollout”. Choose stop, revise, repeat or expand and write the reason. Expansion requires a new scope, not an assumption that support or features continue indefinitely.
If the experience is useful to your own startup, record what is genuinely reusable and what remains client-specific. Keep evidence from a bespoke pilot separate from claims of recurring product revenue or broad market validation.
Sources checked 10 September 2026. This AI-assisted MLAI editorial guide supplies a worked planning example and a functioning arithmetic worksheet, not a tested summary application. Pilot results, customer validation and independent technical, financial or legal review are not claimed. The examples are not regulator-endorsed templates or measured client results.
Frequently Asked Questions
How is a paid pilot different from a prototype?
Should founders take contract work to extend runway?
What should an AI-assisted builder show in an application?
Does applying to MLAI Studio guarantee a project?
Disclaimer: This article provides general information and is not legal or technical advice. For official guidelines on the safe and responsible use of AI, please refer to the Australian Government’s Guidance for AI Adoption →
A practical next step with MLAI
Have delivery capacity alongside your startup?
Already building with AI coding tools and able to review and test what you ship? After checking your capacity and support boundaries, apply with permitted work evidence and realistic availability. MLAI Studio considers suitable builders for scoped, paid project work. Matching is not guaranteed.
Apply for scoped contract work