Custom software development

Custom software built around how your business works

Orders in spreadsheets, documents in emails, updates in someone’s head? I build web apps that bring it all together. We can start with one workflow or the first version of your product.

Tell me about your application

One place for everyday work

A custom app can help you manage orders, share documents with customers or keep track of deadlines. We define who will use it and what they need to do, then use that to scope the first version.

Before suggesting a new build, we check what your existing tools can do. If you need a custom app, we also plan its maintenance and connections to the systems you already use.

When can I help?

A useful starting point is a specific situation you want to change.

  • Orders get lost between files

    It’s difficult to find the latest status, check what was agreed or see who is handling a request.

  • Customers keep asking the same questions

    You resend documents and reply to repeated questions about progress.

  • Your software doesn’t fit the work

    Everyday tasks need extra spreadsheets and manual steps to get done.

  • Your idea needs a first version

    You know who the product is for. You need a working application to show them and test.

What can I build for you?

We choose the parts your project needs and include them in the quote.

  • Order management dashboard

    Orders, statuses, deadlines and documents available to the people who need access.

  • Customer portal

    A place where customers can check their requests and download shared files.

  • First product version

    The most important user journey, working from start to finish and ready to test with your audience.

  • An additional application module

    An extension to a specific area, such as reporting, billing or integrations.

Is this the right step for your business?

We consider the problem, the cost of solving it and what your current tools can do.

Let’s talk if:

  • your current tools require too many workarounds,
  • you know who will use the application and why,
  • you plan to develop the software further and allow for maintenance costs.

A different first step may be enough if:

  • an existing product already supports the workflow,
  • the idea still needs testing with potential users,
  • a small change to your current setup would solve the problem.

A conversation first. Then a clear plan.

Before work begins, we agree on what I’ll build, what it will cost and how we’ll check that it does what you need.

  1. Show me the problem

    Tell me how you work and what takes up your time. I’ll ask about your tools, data and the result you need.

  2. Review the proposal

    I set out the scope, quote and stages, including third-party running costs and anything we still need to check.

  3. Try it as it takes shape

    I show you working parts of the solution. We test agreed examples and gather feedback from the people who will use it.

  4. Put it to work

    I launch the system, show you how to use it and hand over the agreed documentation. We then discuss any next steps.

What do we agree on before starting?

Before quoting, we define the main screens, user roles and connections to other systems. These have a large influence on the amount of work involved.

The plan covers data access, testing and deployment. We also discuss hosting, backups and how problems will be handled after launch.

We agree on the code and documentation handover, so you know how to use the application and what further development will involve.

What application is your business missing?

Tell me who would use it and which task it should make easier. I’ll help you define a first version.

Tell me about your application