Good to know
Ownership, support
and continuity.
Straight answers to the questions owners usually ask before committing. Where we haven't established a public policy, we say so, rather than implying a commitment that isn't confirmed.
Can we keep our existing website or software?
Often, yes. We'd rather connect or extend a tool that's already working than replace it for its own sake. Where a genuine rebuild is the better option, we'll explain why before recommending it.
Do we need AI?
No. AI is one of several ways we might solve a problem, not a requirement. Where it helps, such as repetitive document handling, we'll use it with a person checking the result. Where it doesn't help, we leave it out.
Can we start with one workflow?
Yes. Most engagements start with the single problem costing you the most, not a full rebuild across the business.
Will you recommend existing software instead of a custom build?
Where it can do the job, yes. We compare configuring or integrating what you already use against custom development, and recommend whichever fits the problem, including, sometimes, no technology change at all.
What affects the price?
The number of workflows and systems involved, integration availability and complexity, data quality and migration needs, any custom functionality, and the testing, training and handover a project needs. See "What affects scope and cost" above for the full list, plus any software subscriptions or third-party usage costs identified during scoping.
What happens if the scope changes?
How scope changes are handled is set out in your proposal or contract. In practice, we flag a change before doing the extra work, so you can decide whether it's worth it.
What training and handover are included?
This depends on the project and is confirmed in your proposal. For system and workflow work it typically includes walkthroughs with the people who'll use it and documentation of how it works.
What happens after launch?
We test normal and exception cases before handover, then check the result is being used. Ongoing support beyond that is scoped separately, matched to what was built. See "Ongoing care and improvement" above.
Who owns the accounts, data and custom work?
This is set out in your proposal or contract, agreed before work begins. We don't assume a default position here, and we'd rather confirm it in writing than leave it implied. See our Privacy Policy for how we handle personal information specifically.
Can another provider take over later?
It depends on how a particular system was built and what's agreed about access and documentation at the time. Those specifics are set out in your proposal or contract, not assumed in advance.
