Web applications
Next.js, React and TypeScript
Interfaces for portals, trackers and dashboards.
Custom software
Software built around the work your team does.
When spreadsheets and workarounds no longer fit, I work with you to define what a useful tool should do. I design and build software for your operational workflow, test it with the people using it and prepare a practical handover.
The starting point
Where is the work getting stuck?
I start with the task, the people doing it and the tools you already use. These are some of the situations I can explore with you.
- An important process depends on several disconnected spreadsheets.
- Your team needs a tool that existing software does not provide.
- Managers cannot see the status of enquiries, recruitment or document reviews.
Agreed scope
Define what your team will receive.
A defined operational tool, with requirements, features, testing and delivery agreed in a written project quote.
I confirm the deliverables, responsibilities, timetable and cost in a written quote before work begins. If discovery is needed first, I agree its scope and cost with you separately.
- Requirements and a design grounded in the work your staff need to complete.
- The agreed software, reviewed with you as development progresses.
- Testing against agreed acceptance criteria, with your staff involved.
- Rollout, guidance and handover within the agreed delivery scope.
Project examples
What this can look like in practice.
These are illustrative examples of work I can scope with you. The requirements, supplier access and time your team can give the project determine what is practical.
- A recruitment tracker showing applications, outstanding checks and onboarding handovers.
- An enquiry or referral portal with named owners and clear follow-up stages.
- A management dashboard using agreed measures and named data sources.
- A document workflow for versions, review decisions and approvals.
Behind the build
Technology I work with
I use these technologies across my website and product development. I choose the tools for your project around its requirements, hosting and ongoing support.
How I work
From the current workflow to a supported handover.
I review the work with you as it progresses, test the agreed requirements and make the next responsibilities clear.
Define the useful tool
Walk through the workflow, agree the users and decisions, and set the features and acceptance criteria.
Build and review
Review working versions with you and your staff, with changes to scope agreed before adding work.
Test and hand over
Check the agreed requirements, introduce the software and explain how it will be run and maintained.
Responsibilities
Make ownership clear from the start.
The written scope sets out features, testing and acceptance, hosting, source access, ownership or licensing, third-party costs and maintenance responsibilities. Migration and integrations are included only where agreed. Your organisation retains responsibility for its data, access decisions and operational decisions. This offer focuses on operational administration.
How project costs and ongoing support are agreed- I document the included work, acceptance criteria, testing and handover before delivery.
- You nominate someone who can agree requirements, arrange staff input and accept the completed work.
- Your team provides the agreed access, supplier contacts and time for testing.
- You approve data access and changes to your live processes, and retain responsibility for care and operational decisions.
- We agree who runs the system after handover, including hosting, maintenance and any optional support period.
Work in practice
Related work, with its results and context.
These accounts describe work from my previous roles and businesses. Each case study explains the delivery, evidence and wider context.
Practical answers
A few practical questions
Do I need a technical specification?
No. Start with the problem, the people affected and the tools you use today. I can scope discovery with you before agreeing the software to build and its price.
Would you always build a new system?
I first consider whether existing software or a simpler workflow would meet your needs. A custom build should address a defined gap and have a practical plan for support.
Who owns and maintains the software?
We agree ownership or licensing, source access, hosting and maintenance in writing before development starts. Optional support and improvements have their own agreed scope and costs.
Related services
Other ways I can help with your systems.
I agree the deliverables, responsibilities and cost in a written quote before work starts. A project can draw on more than one service.
A sensible place to begin
Tell me what your team needs to do.
Tell me where the work is getting stuck. We’ll discuss what needs attention and whether there is a useful next step.
- What is happening in your business
- Where it is getting stuck
- Whether I can help
Book a free 20-minute callI’ll confirm a time with you by email.