Application examples

Software built for real business workflows

Business application

RMA portal

Instead of managing return requests and approvals through long email threads, this online application lets customers submit an RMA request themselves — including photos — without waiting on back-and-forth.

Once submitted, the system issues an RMA authorisation number and the customer can track the request through each stage until it is resolved.

Workflow tool

Goods inspection workflow

A rules-based tool for inspecting returned or incoming goods — guiding checks, calculations, and consistent outcomes wherever items need to be received, assessed, and logged.

Custom rules replace manual spreadsheets and documents, so every inspection follows the same logic and produces reliable results. The system handles how different findings affect calculations and decisions throughout the workflow.

Full case study

Quality tool

CMOS image inspection

A lightweight app that analyses microscope sample images, checks brightness variation against specification, and gives technicians a clear pass/fail result with a repeatable log.

Quality decisions become quick and consistent — without manual image comparison, scattered spreadsheets, or debating whether a sample meets the standard.

Websites & landing pages

Your business, explained clearly — before the first phone call

For businesses that want a professional online presence — not a generic page that looks like everyone else's.

A clear place for customers to understand your business

A professional website explains what you offer, how you work, and how to get in touch — before the first phone call. Visitors arrive with context instead of starting from zero.

Clear service pages and a straightforward enquiry path mean fewer repeated emails and back-and-forth calls covering the same details. The site does the explaining; you handle the conversations that matter.

Built to present your business credibly on any device — fast, readable, and shaped around trust from the first scroll.

Business landing page

Independent gym

Website vs landing page

A landing page focuses on one offer or campaign — one clear action. A website holds your full business: services, contact, about, and room to grow as you do.

Why modern sites matter

Older sites are often slow, unclear on mobile, and full of outdated information. A modern site loads quickly, reads clearly on any device, and gives customers a reliable place to check details or get in touch.

Save time on repeat enquiries

Clear service pages, FAQs, and simple enquiry flows answer common questions before they become phone calls or long email threads — light automation that supports your business without replacing personal contact.

Why work with me

You work directly with the person designing and building the site — no template marketplace, no AI-generated layout pasted together, no platform lock-in. Structure and messaging are shaped around how your business actually works.

Choosing an approach

How custom work compares

Select an option to see the trade-offs — honestly, including where a custom build is not the quickest path.

Custom build

Pros

  • Shaped around your message and goals
  • Fast, clean, and yours to keep
  • You work directly with the person building it

Cons

  • Takes longer than downloading a template
  • Higher investment than DIY tools

Good fit

  • Local and service businesses replacing an outdated site
  • B2B companies that need a clearer online presence
  • Anyone tired of explaining the same things by email

Less suited

  • Large e-commerce catalogs with hundreds of products
  • A placeholder page needed live in an hour
  • Teams wanting a full agency plus ongoing marketing department

How it's built

Built to last — maintainable and secure

Maintainability — software should be easy to understand and update as your business changes. When code is structured clearly, new features, fixes, and improvements take less time and cost less — instead of every change feeling risky or expensive.

Security — business applications often hold customer details, internal records, and operational data. Security is considered from the start: who can access what, how information is stored and transmitted, and how the system is protected in everyday use — not added as an afterthought once something goes wrong.

Technologies

TypeScript
Next.js
React
Tailwind CSS
Flutter

How projects run

From first idea to finished product.

A clear, focused process from first conversation to launch. You work directly with me at every stage — no hand-offs to a separate team.

UK-based — direct contact, in person or online.

  1. 01

    Design

    Understand the workflow, the goals, and what the finished product needs to do.

    Every project starts with a conversation about how work happens today — what is manual, what is fragile, and what a better result would look like.

    Requirements, user flows, and key decisions are mapped out together. You review a prototype or clear structure before development begins, so the build stays aligned with what you need.

    Covers: Discovery and planning · Research and prototyping · Validation before build

  2. 02

    Build

    Develop with maintainable architecture, clear interfaces, and dependable logic.

    Development is structured around code that can be understood and extended later — not quick fixes that create hidden debt.

    Features are built in focused stages with testing along the way. You get regular progress updates and can review work as it takes shape, rather than waiting until the end to see results.

    Covers: Architecture and implementation · Testing and quality checks · Reliability throughout the build

  3. 03

    Release

    Launch with confidence, then refine once it's live.

    The project goes live in a stable environment, is checked thoroughly, and is handed over with what you need to operate it day to day.

    After launch, feedback is collected and any fixes or refinements are handled so the product stays dependable and ready for everyday use.

    Covers: Release and handover · Feedback and refinement · Support when needed

Scope, timeline, and budget are agreed before build begins — so the process stays practical and predictable.

What I offer

Areas of focus

A quick overview of what I build — Windows applications, websites, and mobile apps for Android and iOS with Flutter.Native macOS apps are outside my usual scope.

Workflow Systems

Multi-step systems for Windows and the web — designed to simplify repetitive processes and improve operational efficiency.

TypeScript

Internal Tools & Dashboards

Custom operational tools for Windows and the web — designed around structured workflows and day-to-day usability.

TypeScriptNext.js

MVP Applications

Focused first versions for Windows, web, or mobile — designed to validate ideas quickly without unnecessary complexity.

Next.js

Mobile Applications

Android and iOS applications built with Flutter. Native macOS apps are outside my usual scope.

FlutterAndroidiOS

Existing Product Improvements

Redesign, optimisation, maintainability improvements, and cleanup for existing applications.

TypeScriptTailwind CSS

Landing Pages & Websites

Custom websites that communicate your business clearly, improve online presence, and modernise outdated sites — built for your brand, not from templates.

Next.jsTailwind CSS

Questions

Frequently asked questions

Practical answers on scope, pricing, timelines, and what working together looks like.

  • Websites and web apps run in the browser.
  • Desktop applications are built primarily for Windows.
  • Mobile apps are built for Android and iOS using Flutter.

Native macOS app development is not my focus — if that is what you need, I can help you understand the options, but it is not my usual specialisation.

Yes. You do not need a full specification before getting in touch. A short description of the problem, the goal, and what you want to improve is enough to start a useful conversation.
Please refer to the estimated prices for typical project budgets. The final price depends on scope, complexity, content readiness, integrations, and any custom functionality required.
Estimated completion times are shown on the estimated prices page. The final timeline depends on the agreed scope, feedback speed, content availability, technical complexity, and any changes requested during the project.
I review the request, ask any important follow-up questions, and confirm whether the project is a good fit. If it is, the next step is a clear scope, timeline, and price before work begins.
Not always, but it helps. For websites, having text, images, branding, and key company information ready can make the project faster. If content is not ready, the project can still start with structure, layout, and planning.
Yes. Existing websites, unfinished apps, internal spreadsheets, manual workflows, or older systems can often be reviewed and improved. Sometimes the best option is a focused fix; other times a rebuild is cleaner.
Small refinements are normal. Larger changes are handled separately so the scope, timeline, and price stay clear. This avoids vague work, missed expectations, and uncontrolled project creep.
After launch, the project can be handed over, monitored, improved, or supported depending on what is agreed. Some clients only need launch support; others need ongoing updates, fixes, or new features.
Ownership should be clear before the project starts. For custom work, the agreement should define what is delivered, what the client owns, what third-party tools are used, and how the source code or deployment access is handled.
Usually, yes. The details depend on what is already in place and whether it is suitable for the project. If something is outdated, insecure, or limiting, I will explain the options before changing anything.
Yes, when the scope is clear. If the project is uncertain or technically complex, it may be better to start with a smaller discovery or planning stage first, then agree a more accurate fixed price.
AI and templates can be useful, but they do not replace judgement, planning, testing, deployment, maintainability, accessibility, performance, or responsibility for the final result. They are tools, not a complete project delivery process.