Software Solutions

Software that fits how your business works.

Start from the operating problem, not the product name. Tell us what slows the work down today, and we will work out whether the answer is a system we configure or one we build around your procedures.

Start from the problem

Which of these is closest to where you are?

We have an internal process that no ready-made system matches

Permissions, approval stages and data relationships particular to your business, running today across files, spreadsheets and scattered messages. This is where the system is built around the process rather than the other way round.

Custom Software

Configured or custom

Not a contest — a match to the requirement

The choice follows the nature of your requirements: how well defined they are, how much they depend on each other, and how close your way of working is to the ordinary way in your field.

A configurable system we set up

When the requirements are known

  • The work is close to ordinary practice in your field
  • What is needed is order over what exists, not a new procedure
  • You want a faster start on a proven base

We configure the system around your operations and connect it where you need, within what the system itself allows.

A system built around your procedures

When the rules are distinctive and interdependent

  • Business rules or permissions a ready-made system cannot hold
  • Data relationships that depend on one another
  • An internal procedure that is an operational advantage you do not want to change

We analyse and document the procedure, then build the screens and the logic around it, in stages you can start using as they land.

There is no single answer for everyone. Sometimes configuring an existing system is the sounder route; sometimes a purpose-built one costs less over time. We say which after we understand the case.

What Together does

We understand the requirement first, then implement it

  1. We learn the process as it actually runs

    We sit with the people who do the work daily rather than its theoretical description, and document what actually happens — exceptions included.

  2. We separate what gets configured from what gets built

    Part of what you need may already exist in a system and part may need development. We separate the two clearly before quoting.

  3. We implement, connect and see it into use

    Implementation, connection to what you already run, and preparation for going live, in stages you benefit from as they arrive.

Every solution is quoted against its own scope, once we understand how you work and what you need.

Start by describing what slows the work down

We do not need a finished specification to start the conversation. Describe the operating problem and who deals with it, and we will come back with the right route and a quote against the scope.