Three practices, built around shipping.}
subtitle="We organise the studio around three disciplines — websites, apps, and AI automation. Most projects pull from two of them. The good ones pull from all three."
>
{list.map((s, i) => (
0{i + 1} / 03
{s.name}
{s.description}
Explore {s.name.toLowerCase()} →
Includes
{s.subServices.map((sub) => (
{sub.name}
))}
))}
);
}
// -------- Service Detail Page --------
function ServiceDetailPage({ slug, subSlug }) {
const s = SERVICES[slug];
if (!s) return ;
const sub = subSlug ? s.subServices.find((x) => x.slug === subSlug) : null;
const heroTitle = sub ? sub.name : s.name;
const heroSubtitle = sub ? (sub.long || sub.desc) : s.description;
return (
);
}
function ServiceProcess() {
const steps = [
{ n: "01", t: "Discovery", d: "Workshop, audit, and a written success criteria document. ~1 week." },
{ n: "02", t: "Design", d: "Wireframes, prototype, and brand-aligned visual direction. 1-3 weeks." },
{ n: "03", t: "Build", d: "Weekly demos, weekly invoices, daily Slack. 2-12 weeks depending on scope." },
{ n: "04", t: "Launch & care", d: "Smooth go-live, 30-day support window, optional ongoing care plan." },
];
return (
{steps.map((st, i) => (
{st.n}
{st.t}
{st.d}
))}
);
}
function ServiceTools({ s }) {
return (
{s.tools.map((t) => (
{t}
))}
);
}
function ServiceFAQ({ slug }) {
const FAQS = {
web: [
{ q: "Do you build on a CMS or hand-code?", a: "Both — depends on the team behind the site. If you'll edit content weekly, we'll set up a headless CMS (usually Sanity or Payload). If it's mostly static, plain Next.js or Astro is faster and simpler." },
{ q: "Can you migrate from WordPress / Wix / Webflow?", a: "Yes, we do migrations regularly. We preserve URLs, redirect what we can't, and run a content QA pass before launch." },
{ q: "How fast will the site be?", a: "We target 95+ on Lighthouse and a sub-1s Largest Contentful Paint as a baseline. We'll show you the audit before launch." },
],
app: [
{ q: "Native or cross-platform?", a: "We pick based on your team and roadmap. If you have iOS-only audience or hardware-heavy needs, native is usually right. For most B2C, React Native gets you 90% of the polish at 60% of the cost." },
{ q: "Will you handle App Store / Play Store submission?", a: "Yes — including screenshots, descriptions, and the back-and-forth with reviewers. We've shipped 30+ apps without a rejection we couldn't fix in 24 hours." },
{ q: "Can you take over an existing app?", a: "Often yes — we'll do a code audit first to make sure the codebase is salvageable. If it isn't, we'll say so." },
],
ai: [
{ q: "Which model do you use?", a: "Whichever fits — we work with Anthropic, OpenAI, and open-weights via self-hosting. We benchmark on your data before recommending." },
{ q: "What about data privacy?", a: "We support private deployment, on-prem inference, and zero-retention API tiers. We'll match your compliance posture, not the other way around." },
{ q: "How do you avoid hallucinations?", a: "Eval suites before launch, retrieval-grounded prompts, and human-in-the-loop on anything customer-facing. We measure error rates and have rollback plans for every flow." },
],
};
const items = FAQS[slug] || [];
const [open, setOpen] = useState(0);
return (