Question 1

If we own the system, does that mean we're responsible for maintaining it ourselves?

Accepted Answer

Not unless you want to be. Ownership means the system and its data are yours — not that you have to manage the infrastructure. The optional yearly support contract covers updates, backups, security patches, and monitoring. Most clients take it because the peace of mind is worth more than the cost. The ones who don't typically have internal technical capacity or an existing managed hosting arrangement. Either way, the choice is yours — not a condition of the engagement.

Question 2

We've always assumed serious software requires a subscription. Why is that assumption worth questioning now?

Accepted Answer

Because the conditions that made SaaS the only practical option for smaller businesses have changed. A decade ago, owning and running business software required significant internal IT capability and expensive on-premise hardware. Neither is true now. Private cloud hosting is affordable, open-source platforms have matured significantly, and professional configuration services exist at a price point that makes the economics work for businesses well below enterprise scale. The assumption is fifteen years old. The options aren't.

Question 3

Is this a significant disruption to the business during implementation?

Accepted Answer

Less than most clients expect. The implementation runs alongside your existing operations — your team keeps using whatever they're currently using until the new system is ready, tested, and signed off. The transition period is the most intensive part, typically one to two weeks. After that, most teams describe the change as additive rather than disruptive — the new system does more, fits better, and requires less working-around.

Question 4

How does the total cost compare to staying on our current SaaS tools?

Accepted Answer

It depends on your team size and which tools you're replacing. For most businesses between twenty and fifty employees, the total cost of ownership over three years is lower with an owned system than with the equivalent SaaS stack — because the per-seat compounding stops. The crossover point varies, but it typically arrives earlier than clients expect when they run the full three-year number rather than comparing monthly costs. We show this calculation in the proposal — with your actual numbers, not a generic model.

Question 5

What if our needs change significantly after the system is built?

Accepted Answer

Configured systems are not static. The open-source platforms your system is built on are designed to be extended and modified. If your business evolves — new team structure, new sales process, new reporting requirements — the system changes with it. Changes outside the initial scope are handled as discrete engagements, scoped and priced clearly before any work begins. Nothing is locked in place permanently, and nothing changes without your approval.

Question 6

We've had a bad experience with a software implementation before. What's different here?

Accepted Answer

Most implementation failures come from one of three places: scope that wasn't specific enough before work began, a vendor who prioritised speed over fit, or a handover that left the client dependent on the implementor for every change. The way we're structured addresses all three. The specification is written and approved before build begins. The implementation timeline is fixed against that specification. And the handover is complete only when your team is running independently — not when a calendar date arrives.

Question 7

Can we see what we're getting before we commit to anything?

Accepted Answer

Yes. The proposal stage produces a detailed specification document before any build begins — what will be configured, what will be integrated, what it will cost, and what the timeline looks like. You review and approve this before signing anything. There is no commitment required to have that conversation, and no obligation to proceed after seeing the proposal. If the proposal doesn't feel right, you walk away with a clear picture of what the work involves — which has value regardless of whether you proceed with us.

Frequently Ask Questions

Generic

Understanding the Approach

Fit & Suitability

Cost & Investment

Implementation & Timeline

Data Ownership, Security & Control

Support, Maintenance & Responsibility

Flexibility & Customization

Transition & Migration

Long-Term Relationship

Getting Started

Still have questions?

Frequently Ask Questions

Generic

If we own the system, does that mean we're responsible for maintaining it ourselves?

We've always assumed serious software requires a subscription. Why is that assumption worth questioning now?

Is this a significant disruption to the business during implementation?

How does the total cost compare to staying on our current SaaS tools?

What if our needs change significantly after the system is built?

We've had a bad experience with a software implementation before. What's different here?

Can we see what we're getting before we commit to anything?

Understanding the Approach

This sounds different from what I'm used to. How does it actually work?

Why would I choose this over a well-known SaaS product?

What do you mean by 'open-source platforms'? Does that affect reliability?

Is this just a reseller arrangement, or do you actually build and configure the system?

What happens if I want to move to a different vendor later?

Fit & Suitability

We're a 25-person team. Are we too small for this kind of system?

We're in a niche industry. Will the system actually reflect how we work?

We already have some tools in place. Do we have to replace everything?

How do I know if my business is actually ready for this?

We're growing quickly. Will this still fit us in two or three years?

Cost & Investment

How does the cost of this compare to what we're already paying for SaaS tools?

The upfront cost feels higher than just subscribing to software. How should I think about that?

Are there hidden costs we should know about?

What does the optional yearly contract actually cover, and do we need it?

What happens to our investment if we decide to stop working with you?

Implementation & Timeline

How long does it typically take to get up and running?

How disruptive will this be to our day-to-day operations?

What do you need from us during the implementation?

What happens if our needs change partway through the project?

How do we make sure our team actually adopts the new system?

Data Ownership, Security & Control

Who actually owns our data?

How secure is a private cloud compared to a major SaaS provider?

What happens to our data if we stop working with you?

Can we control who inside our business has access to what?

How are backups and data recovery handled?

Support, Maintenance & Responsibility

Once the system is live, who is responsible for keeping it running?

What does day-to-day support actually look like?

What happens if something breaks or goes wrong after go-live?

Will the system stay current, or will it become outdated over time?

What if we want to make changes or add new functionality down the road?

Flexibility & Customization

How much can the system actually be customized to fit how we work?

We have some unusual workflows. Will those be a problem?

Can we start with just one or two modules and expand later?

What are the limits of customization? Is there anything that can't be changed?

If our processes evolve, can the system evolve with us?

Transition & Migration

We have years of data in our current tools. Can it be migrated across?

What if our current data is messy or inconsistently structured?

Will there be a period where we're running two systems at once?

How do we handle the transition without losing productivity?

What happens to our existing tools and subscriptions once we've migrated?

Long-Term Relationship

How involved will you be after the system goes live?

How do we know you'll still be around in three or five years?

Will the people who built our system still be the ones supporting it?

What does the relationship look like as our business grows and our needs change?

What if we're not happy with the system or the relationship isn't working?

Getting Started

We're interested but not ready to commit. What does the first conversation look like?

What information do we need to have ready before reaching out?

How do you assess whether this is the right fit for our business?

What happens after the initial conversation?

Is there any risk in just having an initial conversation?

Still have questions?