Custom business software and web applications

Software built around the way your business works

When off-the-shelf software doesn't fit, we design and build business software and web applications for small and growing businesses: internal tools, customer portals, dashboards and workflow systems. We agree on a written scope with you first, then deliver a working system your team can use, with documentation and training, and support after launch if you want it.

When this helps

Signs a process needs its own software

Custom software earns its cost when a process is central to how you operate and the products on the market make you work around them.

  • Your operation runs on a shared spreadsheet that several people edit, and nobody trusts the latest version.
  • Requests, approvals and job orders move by email and chat, and items get lost between steps.
  • Customers call to ask about the status of an order or request that a portal could show them.
  • A manager waits each week for someone to compile a report by hand from several files.
  • You pay for a large off-the-shelf system, use a small part of it, and work around the rest.
  • An old in-house tool still runs a critical process, but nobody dares to change it.

What we deliver

A working system and what you need to run it

The exact list follows your scope. A custom software project can include:

Discovery notes and written scope

What the system must do, for whom, and what is out of scope, written down and approved before the build starts.

Data model

How your records relate, such as customers, orders, jobs and approvals, designed early so reports and later features have a solid base.

Web application

The working system in a web browser, with the screens, business rules and calculations agreed in the scope.

Admin tools and user roles

Screens for your staff to manage records and settings, with access set by role so each person sees only what their job needs.

Test plan

A written list of what is tested and how, plus the acceptance checks your team runs against the scope before launch.

Deployment

The system set up in its hosting environment with secure configuration, backups and a documented way to release updates.

Documentation

Technical documentation for whoever maintains the system, and user guides for the people who use it every day.

Training

Sessions for administrators and users, built around your real tasks rather than a tour of features.

Support options

Maintenance, updates and help after launch, set out in a separate hosting and support agreement.

How an engagement runs

From the first conversation to a system in daily use

  1. Discovery

    We talk with the people who do the work today, map the current process, and collect the spreadsheets, forms and reports it depends on. First conversations are free. Larger projects may begin with a paid discovery phase, agreed in writing first.

  2. Written scope and quote

    You receive a scope listing features, user roles, data, integrations and exclusions, with a timeline, a price for that scope and the payment terms. The build starts when you approve it.

  3. Design and build in stages

    We design the data model and key screens, then build in stages and review working software with you at agreed checkpoints.

  4. Testing and acceptance

    We test against the scope, then your team runs acceptance checks with real scenarios before go-live.

  5. Launch, handover and support

    We deploy, move existing data across where agreed, train your users and hand over documentation. Your proposal states any defect-fix period after launch. Ongoing support continues under a separate agreement if you choose one.

How we work, from discovery to support

What to expect from us

What working with us looks like

  • Direct access to the people designing and building your system.
  • A written scope and acceptance criteria you approve before the build starts.
  • Security considered from the first design discussion: who can access what, how data is protected, and how the system is kept up to date.
  • Documentation and a planned handover, so the system is not a black box to your business.
  • Clear, written terms on ownership and licensing of code, data and documentation. Ownership and licensing

We build products too. H3lix, LIM5 and Sal3s are software we develop and run ourselves. Running our own software means owning its updates, security fixes and support after launch, and we design client systems with that responsibility in mind. See our products

Related services

Questions

Custom software questions

Should we build custom software or buy a product?

If a product on the market fits most of your process at a reasonable cost, buying is usually faster and cheaper. Custom software makes sense when the process is specific to your business, or when the workarounds cost more than building. Discovery answers that question first, and if buying is the better route, we tell you.

Can you improve a system we already have instead of replacing it?

We start by reviewing its code, data and hosting, then tell you plainly which parts to keep, rework or replace, and why. Rebuilding everything is not always the right answer.

Can we start with a smaller first version?

Yes. A first phase can cover the most painful part of the process, so your team uses it sooner. Later phases are scoped once real use shows what matters most.

Will we receive the source code?

Yes. Once the project is paid in full, you own the custom deliverables we build for you, including their code and intellectual property, unless your proposal says otherwise. Our pre-existing tools, reusable components and products stay ours, and we license them to you for use with those deliverables. Third-party components stay under their own licenses. Our ownership and licensing page explains each case.

Have a process that needs its own software?

Describe what happens today and where it breaks down, and we'll take it from there.