Web Analytics

Custom business systems, portals and workflow applications

Bespoke Web Application Development

ASP.NET and SQL Server web applications built around the way an established business actually works, with paid discovery before development begins.

30 years’ web experience. Direct technical responsibility. Clear scope before a business-critical build starts.


A bespoke application should remove a real operational problem

Off-the-shelf software is useful when the business can adapt to it. A bespoke web application becomes sensible when established processes, data, permissions or customer journeys no longer fit the available tools.

I design and develop browser-based systems for businesses that need more than a marketing website. That may be an internal portal, a customer area, a workflow tool, a reporting system, a questionnaire, an ordering process or a controlled replacement for spreadsheets and manual administration.

The first job is not writing code. It is understanding the process, the users, the information involved and the consequence of getting it wrong.

Main technologyASP.NET, VB.NET or C#, SQL Server and suitable web integrations
Typical workBusiness portals, workflows, dashboards, forms, reporting and customer systems
Best fitEstablished businesses with a defined process and a genuine operational need
Working relationshipDirectly with Neil Patmore from discovery through delivery
Starting pointPaid discovery and technical scoping before a build is proposed
Commercial modelDiscovery defines the answer; development and support are separate phases

A short call can establish whether the project is broadly suitable. Mapping processes, reviewing existing systems, defining data or producing a technical recommendation is paid discovery work.


The warning signs are usually operational rather than visual

A business may have outgrown spreadsheets, shared inboxes or a legacy system long before it has a clear specification for the replacement.

What the business is experiencing

  • Staff enter the same information in several places
  • Important work depends on one person remembering the next step
  • Customers cannot see progress or complete routine actions online
  • Reports take hours because data has to be assembled manually
  • Existing software forces awkward workarounds or exports

What the application must solve

  • One reliable source of current information
  • Clear permissions for staff, customers and administrators
  • Defined workflows with fewer manual handovers
  • Useful reporting without rebuilding spreadsheets each month
  • A maintainable system that can change with the business

The work is designed around the process, not a list of fashionable features

The exact modules depend on the business case, but the build normally combines several of these areas.

Portals and secure areas

Customer, supplier or staff areas with controlled access, role-based information and practical account journeys.

Workflow and administration

Forms, approvals, status changes, notifications and internal tools that replace repeated manual steps.

Data and reporting

SQL Server databases, dashboards, exports and reporting designed around decisions the business actually makes.

Integrations and existing systems

Connections to suitable APIs, payment services, CRM tools, email services or existing databases where the access and documentation allow it.

The application can also include staged migration from an existing process, but data quality and ownership have to be assessed before migration is promised. Where a legacy system must remain available, the transition and rollback route are treated as part of the technical design.


This service is for defined business needs, not speculative feature lists

A bespoke build carries more responsibility than a brochure website. The project needs an owner, a budget, access to the people who understand the process and decisions that can be made when trade-offs appear.

A strong fit

  • An established business has a repeated process worth improving
  • The current system is causing measurable time, risk or service problems
  • Users and decision-makers can take part in discovery and testing
  • The organisation accepts that requirements and edge cases need documenting
  • There is a realistic budget for discovery, development, testing and support

Not a strong fit

  • A startup wants a large platform built before the commercial idea is tested
  • The brief is only a list of competitor features
  • No one can explain the current process or own the decisions
  • The project depends on undocumented third-party access that has not been confirmed
  • The expectation is unlimited changes inside a fixed low budget

The project does not need a perfect specification on day one. It does need a business owner who can explain priorities, accept evidence from discovery and make decisions when cost, speed and complexity pull in different directions.


Published application work provides stronger evidence than anonymous claims

The following case studies describe real custom application projects. They are relevant examples, not promises that another system will have the same scope or result.

Epsilon Lighting web application

A published case study covering a custom web application developed for Epsilon Lighting and the practical business requirement behind it.

Personality questionnaire application

A second Epsilon Lighting case study showing a distinct application with questionnaire logic and a defined user journey.

The discovery phase for a new project starts from its own users, data and operational risks. Existing case studies show delivery experience, not a reusable specification.


A controlled build starts with discovery and keeps decisions visible

1. Initial qualificationYou explain the business problem, current process, users, known systems and the outcome the organisation is trying to achieve.
2. Paid discoveryI map the agreed process, identify uncertainties, review relevant systems and define the questions that must be answered before development.
3. Scope and technical approachYou receive a written proposal covering modules, assumptions, exclusions, responsibilities, delivery stages and the pricing basis.
4. Build in controlled stagesThe application is developed in agreed sections so working features can be reviewed before later parts depend on them.
5. Test with real scenariosWe validate permissions, workflows, calculations, integrations and error paths using representative users and data.
6. Launch, handover and supportThe agreed release is deployed, documented and handed over. Ongoing support, hosting and further development are agreed separately.

Discovery is paid because it produces the decisions the build depends on

There is no responsible fixed price for an application before the process, data, users and integrations are understood. A small internal tool and a multi-role customer portal carry very different work and risk.

How pricing is handled

  • Paid discovery is agreed before detailed investigation begins
  • Open-ended work can use my standard rate of £45 per hour or £360 per day
  • A defined build is quoted by stage or as a clear project where the scope allows it
  • Third-party licences, hosting and specialist services are identified separately
  • Changes outside the approved scope are discussed before work continues

What is not included automatically

  • Unlimited discovery or repeated specification changes
  • Formal penetration testing, legal review or compliance certification
  • Data cleansing or migration not described in the proposal
  • Support for undocumented third-party systems
  • Permanent availability, defect-free software or a guaranteed commercial return

The discovery output remains useful even if you decide not to commission the build from me. Development starts only after the scope, responsibilities and commercial basis are agreed.


Frequently Asked Questions


What kind of businesses do you build applications for?

The best fit is an established business with a defined operational process, a real problem to solve and people who can take part in discovery and testing. I do not position this as a low-cost startup MVP service.


Why is discovery paid?

Discovery involves mapping processes, reviewing systems, identifying risks and producing decisions that the build will rely on. That is substantive work, not a sales conversation.


Can you replace a spreadsheet-based process?

Often, yes, when the spreadsheet is supporting a stable repeated process and the business can define the data, users and rules. Discovery is used to decide whether a bespoke application is proportionate.


Do you work with existing or unfinished applications?

Yes, where the code, database, hosting and access can be reviewed safely. A paid technical assessment may be required before I can say whether extension, repair or rebuild is sensible.


Which technologies do you use?

My established application stack includes ASP.NET and SQL Server, alongside suitable front-end code and integrations. The technical choice follows the requirement rather than being selected for novelty.


Can the application integrate with our other systems?

Potentially. The other system must provide suitable access, documentation and permission. Integration assumptions and failure handling are agreed before they become part of the build.


How long will development take?

Timing depends on the number of roles, workflows, integrations, data migration and review cycles. The proposal sets delivery stages and dependencies after discovery.


What happens after launch?

A separate support arrangement can cover hosting, monitoring, maintenance and further development. Nothing is treated as unlimited ongoing support unless it is written into the agreement.



Related services

These services cover the website, hosting and technical work that may sit around a business application.


Start with the process that is costing the business time or control

Explain what happens now, who uses it and where the current system fails. I will tell you whether the project is suitable for a paid discovery phase.

Scroll to Top