Frequently Asked Questions

We provide digital marketing, website and software development, SaaS and CRM platforms, desktop applications and mobile apps. The unifying idea is that one team is accountable from strategy through build to support, rather than three suppliers pointing at each other when something does not work.

Yes. Most of our work is delivered remotely, with scheduled calls at times that suit your working day. For projects that genuinely need people in a room, we agree that at the start rather than discovering it halfway through.

Book a free consultation through the contact form. We will talk through what you are trying to achieve, tell you what we think it takes, and send a written scope with an indicative cost. There is no obligation and no charge for that stage.

From owner-managed businesses to established companies with internal IT teams. What matters more than headcount is whether there is a clear objective and someone who can make decisions.

Yes. One person is responsible for your engagement and stays with it. You will also have direct access to the people doing the work, because messages relayed through an account manager lose detail.

Routinely, and we are happy to sign yours before any detailed conversation about your project.

Campaigns and tracking are usually live within two to three weeks. Judging performance properly needs enough conversions for the numbers to be stable, which for most businesses means 60 to 90 days. Anyone promising a reliable verdict sooner is guessing.

No, and we keep them visibly separate. You pay the platforms directly for media, and you pay us a management fee. We never take an undisclosed margin on your ad spend.

Yes. We work inside accounts you own wherever possible. If the engagement ends you keep the accounts, the conversion history and the campaign structure intact.

It depends on whether demand for what you sell already exists. If people search for it, paid search usually returns fastest. If they do not know they need it yet, paid social has to create the demand, which takes stronger creative and more patience. We will make a recommendation rather than sell you everything.

A focused marketing site is typically several weeks; a large custom build with a content management layer takes longer. In practice content readiness and approval rounds set the pace more often than development does, so we agree those dependencies up front.

Yes. We build editable content structures so your team can change pages, add articles and publish case studies without needing a developer. The editable regions are defined during the content modelling stage.

Not if the migration is done properly. We map every existing URL, put permanent redirects in place, carry over or improve metadata, and monitor indexing after launch. Ranking loss after a redesign is almost always a redirect problem, not a design one.

We can advise on and configure hosting, and we work with whatever you already have, including standard shared cPanel hosting. We recommend that the hosting account is in your name so you always control it.

Buy, if a standard product fits your process with light configuration. It is cheaper, faster and already tested, and we will tell you when that is the right answer. Build when your process is genuinely different from the market, when licence costs scale badly with your headcount, or when the integration between systems is itself the product.

You do, on completion of the engagement, including the repository and its history. We do not retain licensing over software built for you or hold it hostage through hosting.

Usually. We begin with a code review that reports honestly on what is salvageable, what carries security risk, and where repairing would cost more than replacing.

Yes, and we usually recommend it. An MVP should be narrow in features but sound in architecture. Cutting corners on tenancy, authentication or billing to save a fortnight creates work that is far more expensive to unpick once you have paying customers.

Not comfortably. SaaS needs persistent background workers, a properly sized database and room to scale, which shared hosting does not provide. We size and cost the infrastructure during discovery and keep it as simple as the product allows.

Through an established payment provider that already solves proration, failed payments, dunning and tax. Handling card data yourself is almost never the right decision, and building billing logic from scratch is how codebases become unmaintainable.

Cross-platform makes sense when you need both Android and iOS, the interface is largely standard, and shared code genuinely reduces the work. Native is better when the app leans on platform-specific hardware, needs maximum performance, or must match platform conventions exactly. We recommend based on your requirements rather than a house preference.

Yes, and they should be registered to your business. The app listing, the reviews and the install base are valuable assets, and they should never sit inside an agency account.

Both raise their SDK, privacy and target API requirements periodically, and apps that are not maintained eventually stop being compliant. Our maintenance arrangements cover keeping the app current with those changes.

Because the honest range is too wide for a headline figure to help you. A simple integration and a multi-tenant platform are both software development, and printing one number for both would be misleading. Retained work with a repeatable scope is packaged; project work is quoted after discovery.

Fixed price for well-defined scope, which is most project work. Time-based for open-ended discovery, support retainers and ongoing optimisation. Whichever applies, it is agreed in writing before work starts.

For project work, yes, typically staged payments against agreed milestones so neither side carries all the risk. The schedule is set out in the proposal.

Usually some: hosting, domain, any third-party services the build depends on, and maintenance if you want us to handle it. We list these in the proposal so there are no surprises after launch.

Yes. There is no charge and no obligation, and you keep whatever we work out together. We do it because it is the only reliable way to know whether we can genuinely help before either side commits.

You receive the code, the accounts and documentation written for a developer who has never seen the project. From there you can maintain it in-house, use another supplier, or take a support arrangement with us. All three are legitimate and we do not make the third one artificially easier.

Typically updates and security patching, backups, uptime and error monitoring, periodic performance review, and an agreed response time for issues. The exact scope is set out in the agreement rather than left vague.

Response times depend on the arrangement you choose. Monitoring alerts us to outages and errors automatically, so we usually know before you do.