Skip to main content
Visionnment Estimate value
Menu

Build & Monetize

Commission a Digital-Asset Prototype You Can Actually Accept

Scope one useful prototype, compare implementers, budget review and maintenance, and accept reproducible work instead of a screenshot or vague completion claim.

Blueprint on a workbench becoming a structured website asset

Commission a prototype by defining one useful task and how you will accept its result. Compare implementers against that same task, then require enough editable material and operating guidance for a qualified reviewer to reproduce the work.

A screenshot can demonstrate presentation. It cannot establish that a workflow operates, the delivered files reproduce it or your team can maintain it. Keep those acceptance questions separate from the supplier's claim that the project is finished.

Describe the task before choosing a technology

Write the user, trigger, inputs, expected output and important exclusions. GOV.UK's user-story guidance frames work around a user and their need. Apply that discipline to the small result you can evaluate rather than beginning with a fashionable tool.

For a fictional first project: “A workshop host opens a page and sees three editable setup steps.” The prototype has no login, saved progress, payments or personal data. Those are separate capabilities with separate acceptance work.

Name who can judge the underlying result. If you cannot assess technical quality, arrange an independent competent reviewer before accepting a technical deliverable. A supplier's explanation can help you learn, but it cannot replace that competence.

Try the manual or existing core alternative

Ask whether a document, standard page or existing platform feature already performs the job. Try the smallest supported alternative in an authorized test environment.

For the checklist, a normal page with a numbered list may be sufficient. If the proposed custom work adds no useful capability, retain the simpler option. If the task genuinely requires a reusable component, explain why and test that requirement.

Compare alternatives using the same user result. A custom application should not win because its demonstration includes features you never needed, or lose because a manual option's ongoing work was omitted from the cost comparison.

Compare implementers using the same evidence

Give candidates the same short brief and ask how they would deliver, test and maintain it. Request a relevant example, their actual contribution and the dependencies involved. A portfolio image is a prompt for questions, not proof of operating capability.

Discuss uncertainty openly. When neither party can quote credibly, consider a limited paid discovery or sample with its own clear result. Do not buy a vague “discovery phase” that has no decision or usable deliverable at its end.

The UK government's agile contracting guidance discusses proportionate governance, quality and managing uncertainty in public procurement. It is useful context for delivery questions, not a ready-made private contract or legal advice.

Budget the complete small project

Separate the quoted delivery fee from review time, owner work, hosting, paid dependencies and maintenance. Ask which costs recur and which assumptions change if the prototype becomes a live service.

Use an original fictional budget: $500 supplier fee, $120 independent review, four owner hours valued at an illustrative $25 per hour and $20 for a test environment. The resource comparison totals $740, while direct cash totals $640. Continuing maintenance remains a separate estimate requiring an actual scope and quote.

These figures are not market rates. Their purpose is to prevent a low headline quote from hiding the work needed to accept and operate the result.

Agree deliverables and change authority

Record what is included, who supplies inputs, who reviews work and who approves a change. Name the editable files or configuration, dependency list, test evidence, operating note, recovery route and defect-handling process you expect.

Discuss actual rights, licenses and agreement terms with suitable qualified advice where needed. Paying for work does not answer every ownership or third-party dependency question. Keep the legal judgment with the appropriate adviser and the operational evidence with the project.

Preserve checkpoints. A useful first checkpoint might show the checklist in the test environment with the intended content and a clearly labeled unfinished state. Do not treat that partial demonstration as final acceptance.

Accept a reproducible output and a failure case

Have the reviewer begin with the delivered materials, following the supplier's operating note. Record any undocumented intervention required from the supplier. If it only works while the supplier controls a hidden account or performs unexplained steps, that dependence remains unresolved.

For the fictional static checklist, acceptance can require:

Check Accepted result
Render All three intended steps appear in the test page
Edit Reviewer changes one step in the delivered editable source
Reproduce The changed text appears after the documented update
Failure handling Missing required material is reported clearly, not silently replaced
Removal Reviewer removes the addition without losing unrelated content
Recovery The prior accepted version can be restored by the documented method

Choose a failure case that fits the actual technology. A static page does not need a fictional account-permission test. A saved private workflow does need separate read/write and persistence checks, beyond this checklist scope.

Decide whether to repair, continue or stop

If presentation passes but reproducibility fails, repair the operating delivery. If the result works but nobody needs it, investigate demand before expanding features. If the supplier cannot resolve a material acceptance gap within the agreed arrangement, reduce the scope, seek another implementer or stop.

Keep the accepted version, its dependencies, review result and remaining limitations. Add the recurring operating task to a website SOP. A second operator should know what has been demonstrated and what still depends on specialist help.

Use the digital-asset build guide for the wider path from a useful output to demand and economics. For a WordPress-specific route, compare the core, pattern and plugin learning options. Commissioning can obtain a bounded capability; accepted delivery alone does not create customers or a saleable business.