Something that feels yours.
Purposeful layouts, a considered identity and interactions shaped around your customers and team.
YOUR PROJECT / FROM FIRST IDEA TO CONFIDENT HANDOVERYour next big step.
Your next big step.
Made here in Stevenage.
Your knowledge of the business. Our design and development process. A website or app shaped around the way you work — with a clear route from idea to handover.
Explore a fictional project below. The example below is a browser-only rehearsal. No real agreement, payment or project record is created by this example.
Account setup without sharing passwords ↓ha. / YOUR PROJECT STUDIO
01 / Your brief02 / Scope & agreement03 / Price & payments04 / Build & review05 / Handover & careLess friction. More clarity.
Agree the important tasks first. Try them in staging, refine the details and review against a clear scope.
Know how to run it.
Owner access, useful tutorials, clear running costs and agreed support. Understand what you own and what is licensed.
A CUSTOMER JOURNEY YOU CAN TRYMeet the fictional
Meet the fictional
Field & Fork project.
A small editable restaurant website and QR menu. This example excludes ordering, payments, POS connections and native apps. Its £3,000 illustrative build total is not a ha. offer.
BRIEF / WHAT MATTERS FIRST
A menu your team can keep current.
The useful first version
Three pages: introduction, editable menu and contact. Mobile layout, a table QR linking to the menu, and two review rounds.
The people & permissions
An owner controls access. A nominated menu editor changes prices and availability. No customer database or online ordering in this scope.
Your input
Authorised logo and photographs, menu descriptions, prices, allergen information, business contact details and a named approver. Use sample content during this rehearsal.
Your references
Public design links or a description of your mockup. AI references are welcome; the final design is reviewed and refined around agreed scope.
PROPOSAL / HUMAN REVIEW COMES FIRST
A defined outcome. A written agreement.
The team checks feasibility, delivery costs, rights, security, dependencies and the payment plan. A budget is not an automatic quote. Internal approval is separate from a customer agreeing to the final version.
Included in this fictional example
- Three agreed responsive pages and menu editing
- Named owner and editor access
- QR artwork linked to the menu
- Two review rounds, video tutorials and documented handover
Explicitly outside this example
- Online ordering, payments or kitchen routing
- Hardware, native apps, POS and accounting integrations
- Ongoing unlimited changes or a sales guarantee
- Third-party charges unless itemised separately
The final agreement needs acceptance checks, estimated milestones, dependencies, revision limits, changes, cancellation, payment dates, defect support and rights. It must suit the customer’s business type and any personal-data processing.
PAYMENT / SEE THE WHOLE PICTURE
The build. The schedule. The running costs.
Fictional total payable for the build: £3,000. This illustration uses a total including any applicable tax; actual tax treatment must be confirmed in your proposal. The same total is allocated below, with no added charge in this arithmetic example.
Extended payments are a request, not an offered or approved credit product. Eligibility, start dates, charges, cancellation, missed payments and ownership timing need a separately reviewed agreement. A paid smaller first phase may be a better fit.
£30 / monthIllustrative required hosting & backup cost, paid to supplier from launch.
£60 / monthIllustrative optional support: one agreed hour, no rollover, monthly renewal and 30 days’ notice.
Fictional service prices, not advertised plans. All actual supplier renewals, usage limits and taxes must be itemised. Build repayments are separate and do not buy additional features.
For a real project, the agreed invoice and verified provider or bank receipt must match before work is marked funded. A checkout success screen alone is not reconciliation. Never put card details into an enquiry.
BUILD / REVIEW THE IMPORTANT TASKS
Working software, reviewed in stages.
We agree the setup, use fictional data for development and keep changes visible. Customer feedback is checked against the written acceptance criteria; additions receive a scope and price decision before work starts.
HANDOVER / CONFIDENT FROM DAY ONE
Your people know what to do next.
The handover pack
- Owner login and role instructions, with access invited separately
- Short videos for the agreed everyday tasks
- Source/configuration and data export arrangements
- Asset, domain, service and licence register
- Backup/restore instructions and update responsibilities
- Support contact route, defect period and optional care scope
Clear ownership & access
For bespoke work, transfer of the identified rights follows the agreed payment terms. Your own content and accounts remain yours. Reusable components and third-party software retain their licences.
For a ha. product, you license the product core and keep your business data. Users, support, export and exit arrangements must be agreed. Remove development access that is no longer needed and rotate any temporary credentials.
This download is a sample checklist only. It contains no credentials, customer records or actual project files.
SAFE SETUP / WE GUIDE YOU THROUGH ITTell us what you use.
Tell us what you use.
Keep the keys private.
You do not need to know how to set everything up today. We agree exactly what is required, then give you instructions for your chosen service. Some invitations take minutes; verification and supplier approval can take longer.
01 / What can I put in the enquiry?
Service names, your goals, the types of users and information involved, and public design references. Use fictional examples. Never paste passwords, API keys, card details, identity documents or private staff/customer files. The form checks some recognisable secret patterns, but cannot detect every secret.
02 / How do I give you access?
- Open the provider’s official site and sign in yourself.
- Keep ownership and billing in your organisation’s account where supported; enable multifactor authentication.
- Use its team, developer or collaborator invitation feature.
- Invite the named project contact to the minimum role agreed in your setup plan.
- Record the owner, permission and removal date; never share your password or recovery codes.
We provide provider-specific steps after confirming the actual service and required permission. If it cannot delegate access, agree an alternative before sharing anything.
03 / What if an API key is required?
- Confirm the provider, integration, account owner, permissions and cost limit first.
- Use a separate project and sandbox/test key where available.
- Create the minimum required permissions and set a usage limit or alert.
- Store the secret through the agreed protected deployment or secret-management process; never in this form, a public link or ordinary project notes.
- Test with fictional data, then separately authorise live setup. Revoke temporary keys at handover.
This enquiry form has no secret upload service. No key is required to try the demos.
04 / What about private business information?
First agree what is necessary, who can access it, where it will be held, retention/deletion, security responsibilities and any data-processing agreement. Develop with fictional or appropriately anonymised information. Health, children's or other sensitive records need a separate assessment before collection.
Do not put confidential information into an AI design tool without appropriate permission and provider checks. We agree any use of client material with AI tools separately.
05 / How do I log in as the owner?
Your handover identifies your admin address and named owner account. Accept a separate invitation, set your own password and multifactor authentication, then use the supplied tutorial to manage staff access. No shared “everyone is admin” account. Recovery ownership and support arrangements are recorded.
A clear first step.
A project you understand.
Tell us what you want to improve. We will use your brief to work out the right first release, the real dependencies and a considered proposal.
Tell us about your project ↗