Custom software development
Custom software for the process your current tools cannot handle.
When a spreadsheet, workaround or collection of disconnected tools has become part of how the business operates, a focused application can give that work a more reliable home. I build .NET and SQL Server software for quoting, reporting and specialised operational workflows, including tools that work alongside systems you already use.
Discuss your software projectWhen custom software makes sense
The process is important, repeated and specific to your business.
Custom development is justified when the gap is material enough to support the cost of building and maintaining it, and no suitable product covers the work well. The starting point may be one focused tool rather than a replacement for every system around it.
Shared operations
A spreadsheet has become part of operations
Several people rely on it for pricing, job status, approvals or reporting. Copies are difficult to reconcile, the rules are hard to protect, or one person is the only one who understands it.
Business rules
The workflow depends on business-specific rules
Pricing, approvals, calculations or production steps follow rules that standard products cannot represent without repeated workarounds.
Targeted development
An existing system leaves one important gap
The main platform still does its job, but a focused screen, report or application is needed around it. The new tool can use supported data or interfaces without taking over everything.
What I can build
Focused applications for operational work.
The shape of the software follows the job: a browser-based tool when people need shared access, a Windows application for an established desktop environment, or a reporting and data tool around SQL Server. The useful boundary matters more than the format.
Quoting and document workflows
Bring customer details, pricing inputs and calculation rules together, then generate quotes or production paperwork from the same underlying job data.
Internal workflow applications
Provide the screens, searches, statuses and actions needed to manage jobs, approvals, stock, sales or other defined operational work.
Data and reporting tools
Use SQL Server to hold structured records, apply validation and support reporting. Agree which changes need a history and how incorrect records can be corrected.
Software that works with existing systems
Keep accounting, customer or operational platforms in their existing roles. Where supported access is available, the new application can read or exchange the information it needs through APIs, files or databases.
From workflow to release
Define the work before committing to the build.
A useful specification does not begin with a list of screens. It begins with the people doing the work, the decisions they make, the information they need and the ordinary and exceptional cases the software must handle.
01
Understand the workflow and requirements
Walk through representative jobs from start to finish, including calculations, workarounds, handovers and exceptions. Identify the settled business rules, open decisions, existing systems and responsibilities that will shape the application.
02
Scope a testable first release
Define the users, screens, reports, data and connections included in the first stage, together with what remains outside it. Larger projects can be divided into useful stages so later work is informed by what has already been introduced.
03
Build, test and plan the release
I develop against agreed examples and test representative scenarios before the change is accepted. Data preparation, deployment timing, release responsibilities and recovery arrangements are agreed before the workflow moves across.
Scope and cost
Price a defined first release.
Users, business rules, screens, reports, data preparation, integrations and release work all affect the scope. An initial review establishes the smallest useful version, the decisions needed before development and the boundaries required for a responsible quote.
Project work
Scoped & quoted
The quote covers the agreed first release. Later stages, integrations and ongoing support are scoped separately unless they are included in the project agreement.
Discuss a software projectGuides for planning this work
Questions
Questions before commissioning custom software
Fit and scope
When is custom software not the right answer?
If a proven product already handles the process well, the need is short-lived, or the business cannot support ongoing ownership and maintenance, custom development may not be justified. The review may instead point to configuring an existing product, improving the current system or connecting tools that are already in place.
Do I need a complete specification before contacting you?
No. A clear account of the current workflow, who uses it, where it breaks down and what needs to improve is enough to begin. I can help turn that into requirements, priorities, boundaries and acceptance checks.
Can custom software be delivered in stages?
Yes. A first release can cover the highest-value workflow while later reports, integrations and edge cases remain separate. Each stage still needs a clear boundary, representative test cases and its own acceptance and release plan.
Can the application connect with existing systems?
Often, provided those systems offer suitable access. A connection might use an API, file transfer or database interface. The available access, data ownership and required reliability need to be reviewed before the integration is included in scope.
Ownership and support
Who owns the software and what happens after release?
Ownership, licensing, source access, hosting and support are set out in the project agreement. Before release, we agree who can authorise changes, how faults will be handled and whether ongoing maintenance is included or arranged separately.
Discuss the work
Walk me through one real job.
Describe who does the work, the information they use, the rules they follow and where the current tools cause trouble. You do not need a finished specification. I’ll review whether custom software is justified and what a sensible first stage might include.