Websites
A fast, sharp site, designed and coded rather than assembled from a theme. It loads quickly on a phone on bad signal, which is where most of your visitors actually are.
Your business runs on five tools that don't talk to each other.
I replace them with one system: the website people find you through, the database that remembers them, and the automation that follows up while you work.
Available for new builds
Nothing is broken. That is the problem.
Every tool works. The website collects enquiries. The spreadsheet holds the clients. The calendar holds the week. What nobody owns is the space between them, so that space becomes your evening: copying a name from one place to another, remembering a follow-up, finding out on Friday that Tuesday's enquiry was never answered.
One system closes that space. An enquiry arrives once, and it is a client record, a drafted reply, and a calendar slot before you have finished reading it.
Four parts, built as one thing.
Each part is useful alone. The reason to have them from one person is that they were designed to fit before any of them was written.
A CRM shaped like your business
A client database modelled on how you actually work. Contacts, jobs, quotes, history and stages, in the same system as the site rather than in a separate subscription you log into and forget.
Automation that does the boring half
AI and API integrations that do tangible work: drafting follow-up messages in your voice, summarising long enquiries, routing leads, and connecting the tools you already pay for.
Bookings that fill themselves
Automated follow-ups, reminders and booking. An enquiry arrives, gets logged, gets acknowledged, and moves toward your calendar without you touching it.
Watch an enquiry become a booking.
This is a working demo, not a video. Type a name, send it through, and follow it from the contact form into the client record, into a drafted reply, and into the calendar. Nothing in it is faked, and nothing leaves your browser.
New1 Contacted1 Booked2 Done1 Open the demoWhat actually happens after you message me.
-
01We talk, and I ask awkward questions
One call. What actually eats your week, what you have already tried, and what you would stop doing tomorrow if you could. You get a straight answer on whether I am the right person, including when I am not.
-
02I map the system before I build anything
What information you hold, who touches it, and what has to happen without you. Most of the value is decided here, and it is the step that gets skipped when a project is split across a team.
-
03I build it, and you see it every week
Working software, not mockups and status reports. You use it while it is being built, which is when changing your mind is still cheap.
-
04You own it, and I stay reachable
It runs in your accounts, in your name. You get something documented well enough for a stranger to pick up, and a direct line to me when it needs to grow.
No handoffs, because there is nobody to hand off to.
The person who designs it is the person who wires it
Nothing gets lost between a designer, a developer and an account manager, because there is no gap for it to fall into.
You are talking to the builder
No brief passed down a chain and no relay. You describe the problem to the person who solves it, and you get an answer in the same conversation.
Small enough to say no
I take few projects at a time. That is what makes it possible to turn down work that is a bad fit, which is the only honest way to promise attention.
No client logos. Here is the work instead.
Cardinal Studio is new. I am not going to show you a wall of borrowed logos or invent a number of happy clients. What I can show you is what I build when nobody is paying me to.
The demo on this site
A working pipeline, contact record, drafted follow-up and calendar, running entirely in your browser with no server behind it. It is small, but every part of it does what it says.
Jarvis
A voice assistant that runs on my own machine. It controls applications, keeps timers that announce themselves, and drives coding sessions on my behalf. Nobody commissioned it. It is how I learn the things I later get paid for.
The five questions everybody has.
What does a build cost?
It depends on how much of the system you need, and I would be guessing if I printed a number on this page. What I will promise is that you get a real figure in the first conversation, before any work starts, and that it does not move afterwards unless you ask for something new.
How long does it take?
A site with a working client database behind it is usually a few weeks, not a few months. Automation gets added in layers once the core works, so you have something usable early instead of everything at the end.
I already have a website. Does it get thrown away?
Usually not. If it works and you like it, the sensible move is to leave it alone and build the system behind it. If it is actively costing you enquiries, I will tell you that plainly rather than quietly rebuilding it.
Do I own it, or am I renting it from you?
You own it. The code, the data and the accounts are in your name from the start. There is no licence that expires and no switch I can flip.
You are one person. What if you are unavailable?
Fair question, and the honest answer is not that I am always available. It is that everything runs in your own accounts and I hand over documentation written for a stranger, so another developer can pick it up without me. That is the part most people forget to ask for until they need it.
Tell me what your Monday looks like.
If it involves typing the same name into three different places, we should talk.