Start with the
audit.
Then build what pays off.
We look at the offer, the buyer journey, the current site, and the systems behind it before recommending a build. The result may be a new website, a focused conversion path, or a wider digital system. We define the right scope from the evidence, then build it in a way your team can understand, own, and improve.
A clear path from
finding to system.
We start by understanding the work behind the page: the buyer, the offer, the handoffs, and the systems involved. Then we agree the highest-value scope and move through reviewable milestones with clear ownership.
Karl maps what the business sells, who needs to act, where the current experience loses context, and what the next action should be. The call gives us a useful starting point before any build is scoped.
We turn the findings into page structure, content priorities, integrations, and a written scope. The number of routes and design directions depends on what the audit shows, and we review the choices together.
We build the agreed experience in the appropriate stack, with semantic HTML, accessibility, structured data, analytics, and a staging environment for review. The implementation follows the scope rather than a preset technology package.
We test responsive behavior, browsers, forms, analytics, redirects, and the agreed conversion path. Performance and SEO are checked against the project’s requirements, with findings shared before launch.
We launch with the agreed ownership, documentation, monitoring, and handover. Kratt can remain involved as the managing technical partner, or your team can run the system with a clear next-step plan.
Real systems in the wild.
Different businesses, same care.
Open a live project to see how the work meets the business: clearer information, useful paths to enquiry, and the systems that support the next step. The right build changes with the workflow. See the full portfolio →
discovery site
- Portfolio filters for active listings
- Mobile-first villa detail pages
- Enquiry path connected to each property
platform
- Product story for an operational AI system
- Clear paths into the platform and its workflows
- Product-led UX for a technical buyer
discovery system
- Structured pages for property research
- Internal linking across buyer questions
- Multi-language enquiry journeys
off-plan villas
- Project storytelling for an off-plan launch
- Floorplan, gallery, and unit detail flows
- Enquiry path on every unit
portfolio site
- Type-led portfolio and case-study structure
- Clear route from work to conversation
- Built and deployed as a maintained system
e-commerce
- Editorial product and collection pages
- Story-led path from product to purchase
- Brand voice carried through the experience
Build the site.
Make it findable.
Search is part of the build from the start: semantic structure, structured data, internal linking, useful page titles, and content that answers the questions your buyers actually ask.
If ongoing content or programmatic pages make sense for the business, we scope those as a separate workstream. We measure the agreed search signals over time and use the evidence to decide what to improve next.
They’re selling tools.
We ship sites.
Extend the system
when the work calls for it.
These are not preset packages. We recommend an extension only when the audit shows it will support the workflow, buyer journey, or ownership model we agreed.
Multi-language
Additional languages with a reviewed brand voice, locale-specific content, and a search structure that reflects how each market looks for the offer.
Headless CMS
Sanity, Payload, or the CMS already in your stack, with an editing workflow your team can use and permissions that match how content is approved.
Programmatic SEO at scale
Template-led pages from a carefully defined dataset when the content is genuinely useful and distinct. We validate the matrix, internal links, and quality controls before expanding it.
DTC checkout
Stripe, Shopify, or a custom checkout shaped around the products, approvals, tax, fulfilment, and analytics the business actually needs.
CRM + email loops
Connect forms and enquiry paths to HubSpot, Make, n8n, or the systems you already use, with routing, review points, logging, and clear ownership.
WP / Wix / Webflow port
Content, redirects, structured data, and analytics mapped before moving from a legacy platform. We test the cutover and document what changes.
Six useful questions
before we build.
What happens in the audit?+
Karl leads a 30-minute conversation about the business, the buyer, the workflow, and the systems involved. We look for where time, money, or context is being lost, then explain what we would investigate and what the next sensible step could be. There is no obligation to continue.
Who is a good fit for this work?+
Established teams with a meaningful offer, an existing process, or a digital experience that has become a constraint. You do not need a perfect brief. You do need someone who can share context, make decisions, and help us verify the work in the real operation.
What access and information do you need?+
We start with the workflow and the people who own it. Access is scoped to the audit or build: current pages, analytics, forms, CRM or CMS context, and the relevant constraints. We agree permissions, data boundaries, review points, and responsibilities before implementation.
What stack do you ship in?+
We choose the stack around the requirements, existing systems, and ownership plan. That may be a React or Vite build, an existing CMS, Shopify, or another platform your team can operate. We explain the trade-offs and document the important decisions instead of forcing a default stack.
Who owns and runs the system after launch?+
You choose the operating model. We can remain the managing technical partner for monitoring, improvements, and roadmap decisions, or hand over the code, documentation, and access for your team to run. Ownership and support are written into the scope.
How is SEO handled?+
Technical search foundations are considered during the build: semantic structure, structured data, internal linking, metadata, redirects, and measurement. Ongoing content, multilingual expansion, and programmatic pages are separate workstreams that we scope only when they fit the business and the evidence.
It starts
with the audit call.
In 30 minutes, we understand the business, the current experience, and the systems around it. Then we tell you whether a website build is the right next step, what it should include, and what we would need to make it work. If we’re not the fit, we say so on the call.