FAQ
What people ask before they hire us.
Thirty minutes, no obligation, and no pitch. You describe what is slow, breaking or done by hand, and we ask questions until we understand it. You leave with a written picture of what is actually wrong, whether or not you hire us. If it is not something we should build, we will say so.
We are the tech department for businesses that do not have one. That covers websites, internal tools, AI workflows, automation, cloud setup, and getting found in search and in AI assistants. One team for the whole stack, rather than a web agency, an IT guy and a marketing freelancer who never speak to each other.
Both, depending on what we build. A one-off site can be a single project fee. A system that keeps running, or search work that needs maintaining, is a build fee plus a monthly amount. We tell you which shape applies before you commit, and we do not take a percentage of your sales.
No. Websites are the most visible part, but most of the work is the unglamorous kind: the spreadsheet that four people edit at once, the order form somebody retypes into another system, the report that takes a morning to assemble. If it is repetitive and done by hand, it is probably something we can automate.
Your content, your data and your customer information are yours and leave with you if we part ways. For custom work built for you, ownership is set in writing in the engagement, so nobody has to guess later. If you use one of our existing platforms, you hold a licence while you subscribe rather than owning the engine.
SEO is being found on a search results page. AEO, answer engine optimisation, is being the source an AI assistant quotes when someone asks it a question. Increasingly people ask ChatGPT or Google's AI summary instead of scrolling results, and those answers cite a handful of sources. AEO is the work of being one of them.
Usually yes. We will look at what exists before quoting, because inheriting someone else's code is sometimes cheaper to rebuild than to repair, and you deserve to know which before you pay. We will tell you honestly which one it is, including when the honest answer is to leave it alone.
This is the part most people get burned on. A build that ships and is then left alone stops working within a year: search rankings drift, dependencies break, and the thing nobody owns becomes the thing nobody fixes. We stay on for the running, and the engagement says what that covers before you sign it.
We are based in Singapore and most of our work is with Singapore businesses, which matters for things like PayNow, PDPA and local search. We work remotely and can take on work elsewhere, but we will be straight about it when local knowledge is part of what you are buying.
Within one working day, to hello@cairnco.cloud or the form on the contact page. Both partners see it.
Still not sure it is something we can fix?
Describe the symptom. Working out the actual problem is our job, not yours.
Prefer to read first? Read the guides.