Web applications
SaaS, dashboards, admin portals, and internal tools. Auth, roles, audit logs, multi-tenant data isolation.
- Custom auth and RBAC
- Postgres + typed API layer
- Audit-logged from day one
valUX, UX Studio
A build shop that audits its own work.
Bespoke web builds with Pulse-validated SEO and GEO foundations baked in at launch, not retrofitted six months later. llms.txt, schema graph, Core Web Vitals budget, and schema-per-page on day one. Every build ships with one Pulse Complete Growth audit at month 3, graded against the same rubric we run on client sites.
Built with
Shipped to be found and cited
Two outcomes · One studio
One studio. Two outcomes.
Software you operate, and websites that earn search traffic. Both ship from the same studio, both inherit Pulse-validated foundations at launch.
AXIS_01Software builds
Be Operational.
Products you run, not pages you publish. Multi-tenant data models, custom auth, payments, operator dashboards. Engineered for the workflow that actually exists in your business.
- Web applications + dashboards
- Booking and scheduling systems
- Marketplaces and platforms
AXIS_02Web builds + retrofits
Be Found. Be Cited.
Sites engineered from the schema layer down. Every public route ships with the foundations Google ranks on and the structures AI engines cite from. Foundations baked in, not bolted on.
- Bespoke Next.js + React sites
- Headless commerce
- Schema + GEO retrofit
Full catalogue · Ten services
Pick by what you're shipping.
Each service maps to a delivery shape we have shipped before, with a fixed scope and a named outcome. Three groups: products you run, sites you publish, and specialised work where the brief is sharper than a full rebuild.
GROUP_01
Product builds
GROUP_02
Marketing builds
GROUP_03
Specialised
Booking and scheduling systems
Multi-resource scheduling, calendar logic, payments, and operator dashboards. Built around real availability rules, not generic templates.
- Resource and constraint logic
- Stripe and SCA payments
- Customer + operator surfaces
Marketplaces and platforms
Two-sided and multi-tenant products. Listing flows, vendor onboarding, transactions, payouts, and trust signals.
- Vendor + buyer flows
- Connect-style payouts
- Reviews, disputes, trust
Bespoke websites
Next.js or React marketing sites engineered from the brand layer down. No templates, no theme-shop assembly.
- Component system
- CMS or MDX content layer
- Foundations baked in at launch
Headless commerce
Shopify Hydrogen and Next.js commerce builds. Custom storefront, checkout polish, performance budget that holds.
- Hydrogen or Next.js commerce
- Custom checkout flow
- Performance budget enforced
Website redesign
Replatform or rebuild from a legacy stack. Migrations include 301 maps, schema parity, and AI-crawler access checks.
- 301 redirect map
- Schema and llms.txt parity
- Zero-downtime cutover
WordPress to Next.js migration
Move off PHP and onto Next.js without losing rankings. Content export, URL preservation, schema graph rebuilt.
- Lossless content export
- URL + redirect preservation
- Schema graph rebuilt
Core Web Vitals fix
Performance rescue against the INP, LCP, and CLS budgets Google grades on. Diagnosis, prioritised fixes, verified deltas.
- INP, LCP, CLS diagnosis
- Prioritised remediation
- Before-and-after CrUX evidence
AI feature integration
RAG, agentic workflows, and LLM-augmented product features. Built against a real evaluation harness, not vibes.
- RAG or agent architecture
- Eval harness from day one
- Cost + latency budgets
Schema and GEO retrofit
Bridge to the Pulse retainer. Schema graph, llms.txt, AI-crawler access, and citability rewrites without rebuilding the site.
- Full schema graph
- llms.txt + crawler access
- Citability content pass
The differentiator
Foundations land on day one.
Most build shops finish a site, hand over the keys, and call SEO a phase 2. We ship the foundations at launch, then verify them three months later against the rubric we use on every Pulse audit.
F_01
Schema graph
Organization, Service, FAQPage, BreadcrumbList, and Article nodes wired correctly at every URL, not just the homepage.
F_02
Core Web Vitals budget
INP, LCP, and CLS budgets agreed at scope and enforced through delivery. Lighthouse 90+ at launch is the floor.
F_03
Crawler access policy
robots.txt, llms.txt, and AI-bot allowlists configured for the 18 crawlers that decide whether AI engines cite you.
F_04
Schema-per-page
Every public route ships with route-specific structured data. Templates do not get copy-pasted; the graph is real.
MONTH_03
Pulse Complete Growth audit included. Graded against the same seven-category rubric we run on client sites. The launch state is reproducible. The deltas are real.
How a build runs
Five steps. No theatre.
Sequence, not duration. Discovery and scope are always week 1. Beyond that, the build runs at the pace the surface and the data model actually require.
Step 01
Discovery
Buyer profile, jobs to be done, technical constraints, and the search-visibility starting line for the existing site.
Step 02
Scope
Fixed-scope statement of work. Outcomes named, surfaces named, foundations named. No ambiguous deliverables.
Step 03
Build
Engineering against the scope. Component system, data model, integrations, content, and the GEO foundations together.
Step 04
Launch
Cutover, redirects verified, schema validated, sitemap and llms.txt published, AI crawlers given access on day one.
Step 05
Month-3 audit
One Pulse Complete Growth audit at month 3 post-launch. The score is read against the same rubric Pulse runs on client sites.
Buyer questions
What buyers ask before scoping a build.
What does a typical engagement cost?
Builds are project-scoped, not list-priced. Bespoke marketing sites start lower; SaaS, booking systems, and marketplaces are larger. The fastest way to get a real number is a 30-minute call where the scope is sized against the real surface.
How long does a build take?
Marketing sites typically ship in 4 to 8 weeks. Product builds (web apps, booking systems, marketplaces) range 8 to 20 weeks depending on integrations and the data model. Discovery and scope are always week 1, no exceptions.
What does Pulse-validated mean in practice?
Every build ships with the seven categories Pulse grades: AI Citability, Brand Authority, Content Quality, Technical Foundations, Structured Data, Platform Optimisation, and Agent Readiness. The month-3 audit is run against the same rubric, so the launch state is reproducible.
Do you take on retainers after a build?
Yes. The Pulse retainer is the natural extension. The build ships the foundations; the retainer keeps content, schema, and citability current as engines and competitors move.
Will you work with my existing developer or agency?
Yes, where the split is clean. We can lead the GEO and foundations layer while another team owns brand or feature work. Scope makes this work; ambiguity does not.
Start a build
Book a 30-minute scoping call.
We'll size the surface, name the foundations, and tell you whether a build is the right shape of engagement before any proposal lands.
Prefer email or WhatsApp?Visit the contact page