Advise and design · Consulting and solution design

Get clear on the problem before the build

We work closely with you to understand goals, constraints and opportunities before shaping the right solution, so the project starts with clarity instead of assumptions.

The service

A clear plan is the cheapest part of any project

Consulting and solution design is the work done before anyone commits to a build. We look at how your organisation operates today, the systems and data involved, and what needs to change. Then we shape a solution that fits: sometimes custom software, sometimes an existing product configured well, and often a mix of both. The result is a recommendation and a plan you can act on, with costs and trade-offs in plain view.

It suits leaders who know a process is costing too much but are unsure what to do about it, boards that need a costed case before approving spend, and teams that have inherited systems they do not fully understand. It is also valuable when a past project ran over budget, because unclear scope is the most common reason software projects struggle.

Good solution design is honest. It names the risks, separates what must happen now from what can wait, and says plainly when the answer is to buy rather than build. Because we design, build and run our own products, QuoteCloud, TravelDocs and WebDirector, our advice comes from operating software every day, not just specifying it. That keeps recommendations practical and estimates grounded in how delivery actually works.

Clear scope

A defined problem, priorities and delivery path before money is spent on code.

Buy, build or both

Honest advice on when an existing product fits and when custom work pays off.

A plan you can fund

Phased roadmaps with estimates your board can approve.

Is it right for you?

This is for you if…

  • You know a process needs to change but not whether to buy, build or both.
  • Your board or leadership team wants a costed plan before approving any spend.
  • A previous software project ran over time or budget because the scope kept moving.
  • You have inherited a system and need an independent view of its risks and value.
The problem

Sounds familiar?

If two or more of these ring true, this is where we can help.

  1. 01

    You know something has to change, but not whether to buy, build or both

  2. 02

    A past project ran over because the scope was never clear

  3. 03

    The board wants a costed plan before approving the spend

  4. 04

    You have inherited a system and need to know what you have got

What’s included

What we deliver

Every engagement is scoped to your goals. These are the pieces we are asked for most.

01

Discovery workshops

Structured sessions with the people who do the work and the people who fund it. They surface goals, pain points and constraints early, and build shared agreement on what success looks like.

02

Current state map

A visual map of today’s processes, systems, data and handoffs, showing where time is lost and errors creep in. It turns scattered opinions into a picture everyone can point to and discuss.

03

Options and recommendation

Two or three realistic approaches compared on cost, time, risk and fit, with a clear preferred option. You see the trade-offs openly instead of being steered toward a single answer.

04

Solution architecture

How the recommended solution fits together: components, integrations, data, hosting and security. It gives developers, vendors and your IT team a shared technical blueprint to work from.

05

Phased roadmap and estimate

The work broken into stages that each deliver value, with estimate ranges and assumptions stated. It lets you fund the first phase with confidence and adjust later ones as you learn.

06

Technical due diligence

An independent review of an existing system or a vendor proposal, covering code quality, security, scalability and support risk. It is useful before an acquisition, a renewal or a major investment.

Discovery workshopsProcess and systems mappingSolution architectureBuild-versus-buy recommendationsRoadmaps and estimatesTechnical due diligence
Decisions worth getting right

Three calls that set the budget

Buy, build or both?

Buying an established product is usually faster and cheaper when your process is similar to everyone else’s. Building pays off when the way you work is a genuine advantage, when products force awkward workarounds, or when licence costs grow faster than your business. The most common answer is a blend: a proven product for the standard parts, with custom software or integrations for the parts that make you different.

Big release or phased delivery?

Large single releases concentrate risk: nothing is used until everything is finished, and feedback arrives late. Phased delivery puts a smaller, useful version in people’s hands early, then improves it based on real use. It can feel slower on paper, but it usually reaches value sooner and spends less on features nobody needed. Some changes, such as a full system replacement, need careful cut-over planning either way.

Fixed price or time and materials?

A fixed price gives budget certainty but needs a well-defined scope, and suppliers price in the risk of the unknown. Time and materials is more flexible and often cheaper overall, but needs regular reporting and trust. A common middle path is a fixed-price discovery phase followed by estimated, phased delivery, so the scope is clear before larger commitments are made.

How it runs

How a consulting and solution design project runs

Typical stages and how long each usually takes. Your plan is set during discovery, with working software to see at every stage.

How we work

  1. Listen

    1–2 weeksInterviews and workshops with stakeholders and users to understand goals, constraints and pain points. You get a summary of what we heard and the problems worth solving first.

  2. Map

    1–3 weeksWe document current processes, systems and data flows, and review any existing software or contracts. You get a current state map and a list of gaps and risks.

  3. Recommend

    1–2 weeksWe develop and compare solution options, test them with your team and settle on a preferred approach. You get an options paper and a solution architecture.

  4. Plan

    1–2 weeksWe break the preferred solution into phases with estimates, assumptions and dependencies. You get a roadmap and a delivery proposal ready for your board or leadership team.

Experience

Where we have done this

Real projects for real clients, from our own archive and the products we run today.

Questions

Common questions

Do we have to use you for the build afterwards?

No. The roadmap, architecture and documentation are yours to use with any team, including your own developers or another supplier. The discovery work is designed to stand on its own and give you a fair basis for comparing quotes.

Who from our side needs to be involved?

Usually a sponsor who can make decisions, a few people who do the work every day, and someone who knows your current systems. Their time is concentrated in workshops and short interviews rather than spread across weeks. The quality of the outcome depends far more on having the right people in the room than on the number of meetings.

Will you recommend one of your own products?

Only where it genuinely fits. Sometimes QuoteCloud or WebDirector solves part of the problem well, and we will say so and explain why. Equally, we will point you to other products or a custom approach when that is the better answer. An options paper that compares alternatives openly is part of every engagement.

How accurate are the estimates?

Accuracy improves as uncertainty falls. Early estimates are given as ranges with the assumptions stated, so you can see what would move them. The first phase can usually be estimated tightly, and later phases are refined as work progresses. We would rather give you an honest range than a single number that looks precise but hides risk.

Can you review a proposal from another supplier?

Yes. We can assess whether the scope matches your needs, whether the technical approach is sound, whether estimates look realistic and what risks are missing. It is a practical way to get a second opinion before signing, and the findings are written for decision makers rather than only for developers.

How do you approach new software projects?

We start with solution consulting and discovery: analysing your needs, systems and goals. From there we design a solution that improves efficiency, reduces cost and supports long-term growth.

Need software built around the way your business actually runs?

Whether you’re planning a new SaaS product, custom business software, a mobile app or a better digital workflow, we’d love to hear what you’re working on.