Refspan
Menu

When spreadsheets and email can’t keep up.

If your team chases requests across inboxes and spreadsheets, a web application can put the whole process in one place. I start with the workflow, scope a focused first release, and fix the price before building.

Start with the problem, not the technology.

A first release you can use sooner.

We agree the smallest version that solves the core problem, then build it in milestones you review. Later ideas are planned separately, so the first release stays within its fixed price. The technology, such as Laravel, React or Next.js, is chosen for the job, and the code is yours at handover.

Two projects I have built, with what each one does: Salah Auto Hub and Islah Trust.

If you are planning a portal, read how to write a client portal brief.

Customer portals

Let clients sign in to upload documents, track requests or see their account, instead of emailing back and forth.

Internal tools

Turn a process your team repeats every day into an application with the right roles and permissions.

Connected systems

Link the services you already use. I check their APIs and limits before committing to a price.

Project questions

Have a question about your own project? Send a short brief and I’ll give you a straight answer myself.

Ask about your project
Do I need a technical specification?

No. Start with what you want people to do and the problem you need to solve. Sketches, spreadsheets you use now, or examples you like are all useful.

Who owns the code?

You do, once the work is paid for. The code, hosting and accounts are in your name at handover.

Can you work on an existing application?

Share the technology and the changes you need. I assess the code and access requirements before confirming whether Refspan is the right fit.

How is a web application quoted?

The quote follows an agreed scope, with a fixed price for the first release. Where requirements are uncertain, we agree a small piece of investigation first, so you are not paying for guesswork.

Plan your project

  • Web applications
  • 3 min read

How to plan a client portal: requirements checklist

Plan a client portal around users, permissions, workflows, integrations and a manageable first release. A practical requirements checklist.

Get a fixed quote for your project.

Send your brief, designs, or a link to your current site. I agree the scope and price with you before any work starts.

Describe your workflowCall 07424 245857Message on WhatsApp

A few sentences is enough. I’ll ask about anything I need.

Last updated

Get your free homepage preview

Tell me about your business. I’ll design a preview of your new homepage and show it to you within 48 hours, before you pay anything. If you decide not to go ahead, you owe nothing.

What should the homepage get people to do?

I only use these details to prepare your preview and reply to you. Privacy notice.

Chat on WhatsApp

Scan the code with your phone camera to start a chat on your phone.

QR code that opens a WhatsApp chat with Refspan

07424 245857

Open WhatsApp Web (opens in a new tab)

Or chat from this computer (opens in a new tab).