SetFrame is a studio that builds websites and the systems behind them for businesses that run on inquiries, appointments and follow-up.
The focus is narrow on purpose: turn the trust a business already earns into booked calls, and stop the leads, replies and paperwork that quietly slip through the cracks in between.
How the work is approached
A system is only worth what changes after it ships. A dashboard that nobody opens, an automation that saves four minutes a month, a redesign that moves nothing — all of it is cost dressed as progress.
So every project is written down as a change before it is built: what the business does today, what it should do instead, and how that gets measured. If a build cannot be described that way, it is the wrong build.
Two businesses that look identical from the outside almost never leak in the same place. One is losing people at the first reply, another has plenty of enquiries and no way to keep track of them, a third is fine until the person holding it together takes a week off.
A template answers all three the same way. The work here starts from a conversation instead, and what gets built follows from what that conversation finds.
Proposals are easy to agree with and hard to judge. A working version is neither — it either does the thing or it does not, and you can tell in a minute without knowing anything about how it was made.
That is why a preview comes before a signature. It removes the part of the decision that runs on trust alone.
Which stack, which service, which model — those are implementation details, and treating them as selling points asks you to evaluate something you have no reason to have an opinion about.
What matters is the reply that goes out at 11pm, the paperwork that files itself, the enquiry that becomes a booked call. The machinery behind that is the studio's problem to get right.
Anything that needs babysitting gets abandoned in the first busy week, and a system abandoned in month two was never worth building.
So the standard is durability: fast, accessible, understandable by whoever comes next, and owned outright by the business it serves. Nothing is held hostage — the code, the content and the accounts are yours.
What working together looks like
You talk to the person doing the work. There is no account layer in between, so nothing gets lost on the way to whoever is actually building it, and questions get answered by someone who knows the answer.
Scope and price are agreed before anything starts, and they do not move while the work is underway. Feedback runs until the thing does what it was supposed to do — that is part of the project, not an extra.
After launch you are not locked in. Ongoing improvement is available if it is useful, and if your own team would rather take it over, everything is documented well enough for them to do that.
Step by step, that runs as three stages: a conversation, a working preview, then a system that keeps running.
One conversation about where your business is leaking, and what stopping it is worth.
