What exists before the work
A browser prototype demonstrates the intended screens and happy path. It uses test data, has incomplete authentication, no durable audit trail, and no repeatable production deployment.
PROTOTYPE → PRODUCTION EXAMPLE
From a signup demo to software real customers can use.
In this illustrative project, a customer can create an account, verify access, provide the required details and see that signup is complete.Provenance
This is an illustrative internal artifact created to make the delivery and evidence standard inspectable. It does not claim a customer, customer result, testimonial, or historical engagement.
Who will use the result
A small-business customer signing up without support, accepted by the operations owner responsible for onboarding.
What needs to change
The demo can show intent but cannot safely accept real identity and business data, recover from partial failure, or prove which onboarding step completed.
What the software must do
A customer creates an account, verifies access, supplies the agreed onboarding data, and reaches a durable accepted state that the operations owner can inspect.
WHAT IS INSPECTED
What we check before agreeing the work
- Prototype walkthrough and screen inventory
- Repository structure, dependencies, and deployment configuration
- Authentication and authorization boundary
- Data model and handling of sensitive fields
- Failure, retry, logging, and support paths
ACCEPTANCE CHECKS
How we check that it works
- 01A new customer completes signup in the agreed production environment.
- 02Interrupted verification can resume without duplicate or inconsistent records.
- 03Unauthorized users cannot see or change another customer's onboarding data.
- 04The operations owner can identify status, failure reason, and next action.
- 05Automated checks and a recorded acceptance test support handover.
A customer can complete signup without a developer's help, and the business can verify that it succeeded.
OWNERSHIP & HANDOFF
- Customer-owned repository and deployment project
- Production and recovery runbook
- Environment, account, and access inventory
- Acceptance evidence and automated checks
- Known limitations and defined correction window
EXPLICIT EXCLUSIONS
- The rest of the future customer portal
- Billing, subscription, and enterprise SSO unless separately scoped
- Unknown migration from legacy customer records
- Native mobile applications
- Additional roles and workflows beyond onboarding
Have something similar in mind?
Describe your project in plain language to receive a preliminary proposal with a price range, timeline and downloadable PDF. No call or approved minimum budget is required to receive it.
Describe your project →