Websites that adapt to every visitor.
Every company needs a website. Most get a CMS with plugin rot, security patches and an admin nobody enjoys. My smart websites are different: proper Ruby on Rails builds, edited through AI in your client portal, and clever enough to show every visitor the version of your story they came for.
Launching soon
The full Smart Websites offering is nearly ready. Leave your email and be the first to see it, plus early launch offers.
Rails, not a CMS
Your website is a real engineered build: fast, secure, no plugin treadmill, no template ceiling. Content lives as structured data, so the site can do things a page builder never will.
Edited through AI, in your portal
Change copy and images yourself: describe the change in plain language in your client portal, AI drafts it in your brand voice, you approve, it goes live. No CMS training, no agency round trip for small changes.
Smart by default
Your site adapts: the content matches the ad a visitor clicked, remembers returning visitors with their consent, and meets people where they are in their journey.
The smart content engine
Ad matching
A visitor from your LinkedIn ad lands on a page that continues exactly what the ad promised. Ad and page are written as a pair and generated as one URL.
Personalisation with consent
Returning visitors see the site they know. Interest is remembered in their consent cookie, first party only, and nothing is stored before they agree.
A/B and multivariate testing
Variants run against real conversions, assignment stays sticky per visitor, and the winner is data, not opinion.
Peace of mind
What happens when something goes wrong?
The honest answer for most software: nobody knows until a customer complains. Here, the worst case is engineered for, twice. Everything is tested before it ships, and everything reports on itself while it runs.
Tested before it ever ships
Every feature is first written down as expected behaviour in plain language: when a customer does this, the system does that. Then the code is written until every one of those checks passes, and they run automatically on every single release. Developers call this TDD and BDD; for you it means a release only goes out when everything it promised is verified, and features that worked yesterday are re verified today.
Watched live, around the clock
Every web app and every Solidus store I run is wired into Sentry, the industry standard for live error monitoring. The moment a single customer hits a problem, it is reported automatically: which page, which action, which device, and exactly where in the code it happened. No waiting for someone to email a complaint that starts with "it does not work".
Fixed before it spreads
Because the alert arrives with the full technical context, the fix starts immediately, often before a second customer ever sees the problem. Compare that to the usual routine: a customer gives up, maybe complains days later, support asks them to describe what happened, and a developer tries to guess. That routine is where shops quietly lose revenue.
No vibe coding surprises
Vibe coding is the industry’s new habit: let AI write the software wholesale and ship whatever comes out. It feels fast, right up until something silently changes: an input, an output, a calculation, a payment flow. I use AI deliberately, and only where it cannot hurt you: repetitive tasks, frontend structure, scaffolding that I finish, review and perfect by hand.
The critical path, everything that touches money, data or the behaviour of your business, stays hand built and controlled, protected by the same automated checks described above. Nothing changes how your system behaves without being caught, because the checks would fail before a release ever goes out. If you take payments or operate anywhere near the financial world, that is the difference between a bug you never hear about and a story that damages your reputation, or worse, ends in front of a judge.
Most agencies hand over at launch and wait for you to report problems. My systems report on themselves, and I am watching.
Live monitoring runs on sentry.io.
How every engagement runs
Enterprise discipline, one person
Anyone can promise quality. I run every engagement through systems that prove it: a real client portal, legal clarity before work begins, and evidence for every release. This is what working with me actually looks like.
Your own client portal
Every client gets a seat in the Keferboeck Hub: onboarding, documents, dashboards and live project links in one place. Structured from day one, so nothing important ever lives in a lost email thread.
Legal clarity before work begins
Contracts, terms and insurance documents live in a portal vault. Signed versions are locked forever, every view and download is logged, and onboarding includes a formal review and acceptance step, with the option to hand it straight to your legal team.
Every release documented
Production releases are versioned, timestamped and written up: what was added, what changed, what was removed. You can always answer the question "what exactly went live, and when", because the record exists.
Tests gate every release
The full TDD and BDD suites must pass before anything reaches production, and the runs are recorded as evidence, with coverage tracked. A release that has not proven itself does not ship.
Verifiable by third parties
Critical business logic, how a calculation works, which legal documents a signup binds, is written up in plain language, approved by you, frozen at that state, and exportable as a PDF in English and German for your auditor. Changes reopen the approval, so the record never drifts from reality.
Security tested
Major production releases get web application security testing on top of the automated suites, grounded in formal offensive security training. Systems that hold customer and payment data deserve nothing less.
Insured, properly
A comprehensive insurance package is in place through the broker JMG: professional indemnity, public liability, employers liability and cyber cover. The insurer knows explicitly that my systems handle accounting grade workloads for SaaS products, loan interest and repayment calculations included, so exactly that work is covered.
And if I fall under a bus?
Everything is documented: architecture, decisions, processes, tests and the code itself, all written for the next person to pick up cold. If anyone else ever needs to take over, for any reason, the handover is instant and smooth. No key person risk, no vendor lock in, no hostage code. Very few agencies can honestly offer that; almost no freelancer can.
The other side of that coin: I play a central role in every project and I take responsibility for it. I do not vanish the moment a better offer turns up. The setup is simply built to change as you grow. When the workload gets massive, parts of what I do can move in house, your team owns the day to day, and I focus on whatever challenge matters at that stage of the growth cycle. That is the plan working, not a breakup.
How working with me runs, in full→Curious what your smart website would look like?
We start with the free workshop: your site, your customer journeys, your plan. You keep the plan whatever you decide.
Book the free workshop