Solutions/Websites & Business Apps
Business solution / Build something useful

A clearer website.
A useful app.
Built for your business.

You may need a website that explains your services, a place for customers to track requests or an app that helps staff do their work. We help you decide what the first version needs, design it and build it. AI is added when it helps with a real task.

For business owners who need a clearer website, a customer login area or an app for a specific task.

The business case

A useful idea.
Where do you start?

Explain your services, give customers a place to track requests or make a staff task easier. We help turn the idea into a clear first version.

01

Customers do not understand your offer

The website makes it hard to find services, prices or the next step.

02

Simple tasks need too many messages

Customers or staff have no clear place to submit requests and see updates.

03

The idea feels too big to start

You need help deciding which features are essential for the first working version.

How it works / step by step

See what happens.
Step by step.

Agree the main task, review the screens, build the first version and test it with real examples before launch.

Select a stage to see what goes in, what comes out, and where your team stays involved.

01UnderstandUnderstand who needs it

Agree who will use the website or app and the main job they need to do.

STARTS WITH

An idea and the people who need it

YOU GET

A clear job for the website or app

You decide what matters for the first version.
02DesignShow the screens

Review the main pages and steps so you can see how it will work.

STARTS WITH

The main tasks and your feedback

YOU GET

Screens showing how it will work

We review the important screens before finishing the build.
03BuildBuild the first version

Create the pages, features and software connections listed in the plan.

STARTS WITH

Approved screens and a feature list

YOU GET

The agreed pages and features

Extra features are discussed before adding them.
04TestTest everyday use

Check the main tasks, phone screens, access rules and what happens when something goes wrong.

STARTS WITH

A working version and example tasks

YOU GET

Test results and issues to fix

The agreed tasks and access rules are checked before launch.
05LaunchLaunch and explain it

Put it online, hand over the agreed access and show your team how to use it.

STARTS WITH

A checked release and account access

YOU GET

A live website or app with instructions

Later improvements follow feedback from people using it.
What we can build for you

Know what you get.
Know how it helps.

These are the parts we can include. Your written quote lists the tasks, tools, quantities and checks included in your project.

01 / PRODUCT DEVELOPMENT

A clear starting plan

Agree who will use it, what they need to do and what the first version includes.

  • Agree who will use it, what they need to do and what the first version includes.
  • A written list of what is included
WE AGREE WITH YOU FIRSTThe first task and examples to test
02 / PRODUCT DEVELOPMENT

Screens to review

See how the website or app will look and work before we finish the build.

  • See how the website or app will look and work before we finish the build.
  • A named person to keep information current
WE AGREE WITH YOU FIRSTInformation, quantity and languages
03 / PRODUCT DEVELOPMENT

The working website or app

Build the pages, features and connections listed in your proposal.

  • Build the pages, features and connections listed in your proposal.
  • The agreed tools connected together
WE AGREE WITH YOU FIRSTSoftware connections and permitted records
04 / PRODUCT DEVELOPMENT

AI where it helps

Add useful features such as document search or draft writing when agreed.

  • Add useful features such as document search or draft writing when agreed.
  • A clear next step when staff help is needed
WE AGREE WITH YOU FIRSTPeople who check and approve
05 / PRODUCT DEVELOPMENT

Testing and launch

Check the main tasks, mobile screens, access permissions and important error cases.

  • Check the main tasks, mobile screens, access permissions and important error cases.
  • Checks using examples from your business
WE AGREE WITH YOU FIRSTTest cases and what success means
06 / PRODUCT DEVELOPMENT

Training and next steps

Hand over the agreed files and accounts, explain daily use and list possible later improvements.

  • Hand over the agreed files and accounts, explain daily use and list possible later improvements.
  • Instructions for daily use and common problems
WE AGREE WITH YOU FIRSTTraining, accounts and optional support

Planning, a first build and later improvements can be separate projects. AI is included only if agreed and useful for the task. Any paid software and usage costs are explained separately.

An example / sample information

A customer signs in.
Checks their request.
No chasing needed.

These example screens show how the work could look. We build your version around your business and the tools you use.

A concrete business example

A place for customers to see what happens next.

A service business wants customers to stop chasing request updates. The first app version lets a customer sign in, submit a request and see a status updated by staff. Customers only see their own requests. File uploads or other extras can be planned for a later version.

01 / WHERE IT FITS

Service businesses and shops

Build a website that explains your offer and makes enquiries or purchases easier.

02 / WHERE IT FITS

Teams with a repeated task

Create a customer or staff app for requesting work, checking status or finding approved information.

Start with one problem

Start where you are.
Extend with purpose.

Keep the tools that work. Decide what needs to be added, connected, or operated on an ongoing basis.

01

Start with a plan and screens

Make the idea clear before committing to the full build.

02

Build the essential version

Include the main task people need, with a written list of features and checks.

03

Add more after real use

Use feedback to decide which extra features are worth building next.

What is included?

Your quote lists the pages, features, user roles, content, software connections and launch work included. Extra features, AI functions and ongoing development are agreed separately.

What we need from your team

What we need
to get started.

We explain which information we need, who checks the work and who looks after it once it is in use.

01

The people using it

Who needs access and what should they be able to do?

02

Your content and examples

Service information, branding and examples of the records or requests involved.

03

A person to make decisions

Someone who can review the screens and decide what belongs in the first version.

How we check the results

Check the system.
Measure what changes.

We test that it does the job we agreed. To see whether it saves time, we compare the task before and after your team starts using it.

01 / EVALUATION

Can people use it?

Check whether users complete the main task without getting stuck.

02 / EVALUATION

Does it work on their devices?

Check the agreed pages and steps on phone and desktop screens.

03 / EVALUATION

Is it ready to run?

Check access, important failures, account ownership and the instructions your team needs.

Getting set up and help afterwards

Ready to use.
With help to
get started.

See how we work ↗
01 / GETTING IT SET UP

Set up, test and show your team.

We understand the task, build the parts you choose, test them and show your team how to use them. Your quote explains the accounts and ongoing costs.

02 / HELP AFTER LAUNCH

Choose the support you need.

After launch, you can choose maintenance, fixes and agreed improvements. Hosting and other paid services are identified separately from the build.

Before we begin / Websites & Business Apps

Your questions.
Plain answers.

Answers about what we can build, what we need from you and how your team uses it.

Have a task you need help with?Tell us about it ↗
01Does it need AI?

Only if AI helps a specific task. A clear website or straightforward customer portal may be the right answer without it.

02Can we see the design before it is finished?

Yes. We review the main screens and steps before completing the build.

03Can we start small?

Yes. We agree the essentials for the first version and keep later ideas on a separate list.

04Who supplies the text and images?

We agree that in the proposal. Writing, photography and moving old content can be included when listed.

05Who owns the website and accounts?

Your agreement explains ownership, licenses, account access and ongoing costs before the project starts.

Your next useful move / Websites & Business Apps

What would you like
your website or app
to do?

Tell us who will use it and the task you want to make easier.

Discuss your website or app
You explain the problem.
We help work out the next step.

Tell us what happens today. We will help you work out what to improve first.