196 lines
8.5 KiB
TypeScript
196 lines
8.5 KiB
TypeScript
import type { ServiceDetailContent } from '$lib/types/service-page';
|
||
|
||
const discoveryCallUrl =
|
||
'https://cal.mifi.ventures/the-mifi/30min?utm_source=website&utm_medium=cta&utm_campaign=schedule_call&utm_content=mvp_arch_launch_page';
|
||
|
||
export const pageContent: ServiceDetailContent = {
|
||
hero: {
|
||
title: 'MVP Architecture & Launch for Early-Stage SaaS',
|
||
subtitle:
|
||
'Shipping fast is good. Shipping chaos is expensive. I help early-stage SaaS teams build MVPs that move quickly without creating frontend debt, fragile CSS, or structural problems that slow iteration six months later.',
|
||
bookingLinkTitle: 'Book a discovery call',
|
||
bookingLinkUrl: discoveryCallUrl,
|
||
secondaryCta: {
|
||
href: '#approach',
|
||
label: 'See how I work',
|
||
umamiEventLabel: 'see how i work',
|
||
},
|
||
},
|
||
tocItems: [
|
||
{ label: 'The common MVP pattern', href: '#common-pattern' },
|
||
{ label: 'What a good MVP foundation looks like', href: '#good-foundation' },
|
||
{ label: 'My approach', href: '#approach' },
|
||
{ label: 'What changes within 1–2 weeks', href: '#what-changes' },
|
||
{ label: 'Engagement options', href: '#engagement' },
|
||
{ label: "Who it's for", href: '#who-its-for' },
|
||
{ label: 'FAQ', href: '#faq' },
|
||
{ label: 'Get in touch', href: '#final-cta' },
|
||
],
|
||
navItems: [
|
||
{ label: 'Home', href: '/', umamiEventLabel: 'home' },
|
||
{ label: 'My approach', href: '#approach', umamiEventLabel: 'approach' },
|
||
{ label: 'Engagement', href: '#engagement', umamiEventLabel: 'engagement' },
|
||
{ label: 'FAQ', href: '#faq', umamiEventLabel: 'faq' },
|
||
{
|
||
label: 'Book a call',
|
||
href: `${discoveryCallUrl}-navigation`,
|
||
umamiEventLabel: 'book-call',
|
||
},
|
||
],
|
||
sections: [
|
||
{
|
||
id: 'common-pattern',
|
||
headingId: 'common-pattern-heading',
|
||
heading: 'Most MVPs are built for speed—few are built for iteration',
|
||
paragraphs: [
|
||
'Early MVPs often prioritize backend logic and feature delivery. The frontend becomes an afterthought—functional, but brittle. Six months later, every new feature feels heavier than the last.',
|
||
'Common symptoms:',
|
||
],
|
||
bullets: [
|
||
'Poor separation of concerns',
|
||
'Backend-heavy architecture with fragile UI',
|
||
'Repeated components instead of reusable systems',
|
||
'Spaghetti CSS and specificity wars',
|
||
'Accessibility postponed',
|
||
'"We\'ll clean it up later" decisions compounding',
|
||
],
|
||
trailingParagraphs: ["Speed isn't the problem. Structure is."],
|
||
},
|
||
{
|
||
id: 'good-foundation',
|
||
headingId: 'good-foundation-heading',
|
||
heading: 'MVP does not mean throwaway',
|
||
paragraphs: ['A well-built MVP is minimal—but intentional.', 'It includes:'],
|
||
bullets: [
|
||
'Clear separation between layers',
|
||
'Reusable, composable frontend components',
|
||
'Tokenized design systems (color, spacing, typography)',
|
||
'Clean, maintainable CSS architecture',
|
||
'Accessibility baked in from day one',
|
||
'A simple, predictable deployment path',
|
||
],
|
||
trailingParagraphs: [
|
||
'You can move fast and build correctly at the same time.',
|
||
],
|
||
footerLinks: [
|
||
{
|
||
label: 'Hands-on SaaS architecture',
|
||
href: '/services/hands-on-saas-architecture-consultant',
|
||
},
|
||
{
|
||
label: 'Fractional CTO for early-stage SaaS',
|
||
href: '/services/fractional-cto-for-early-stage-saas',
|
||
},
|
||
{
|
||
label: 'Stage-aligned infrastructure',
|
||
href: '/services/stage-aligned-infrastructure',
|
||
},
|
||
],
|
||
},
|
||
{
|
||
id: 'approach',
|
||
headingId: 'approach-heading',
|
||
heading: 'Architecture through implementation',
|
||
paragraphs: [
|
||
"I don't deliver diagrams and disappear. I work inside your codebase.",
|
||
'My approach:',
|
||
],
|
||
orderedBullets: [
|
||
'Fix the CSS foundation first.',
|
||
'Extract and standardize reusable components.',
|
||
'Introduce design tokens to prevent duplication.',
|
||
'Align frontend and backend boundaries.',
|
||
'Improve accessibility and semantics incrementally.',
|
||
'Keep shipping while refactoring.',
|
||
],
|
||
trailingParagraphs: ['No rewrite mandates. No velocity freeze.'],
|
||
},
|
||
{
|
||
id: 'what-changes',
|
||
headingId: 'what-changes-heading',
|
||
heading: 'What teams notice quickly',
|
||
paragraphs: [
|
||
'In most cases, teams feel the difference within 1–2 weeks once foundational issues are corrected.',
|
||
"You'll see:",
|
||
],
|
||
bullets: [
|
||
'Faster feature implementation',
|
||
'Lower bug rates',
|
||
'More consistent UI',
|
||
'Safer refactors',
|
||
'Increased release confidence',
|
||
'Better team morale',
|
||
],
|
||
trailingParagraphs: [
|
||
"It's all one big ball of yarn—clean up the foundation and everything moves more smoothly.",
|
||
],
|
||
},
|
||
{
|
||
id: 'engagement',
|
||
headingId: 'engagement-heading',
|
||
heading: 'How we can work together',
|
||
subsections: [
|
||
{
|
||
heading: 'MVP Architecture Engagement (fixed scope)',
|
||
bullets: [
|
||
'Codebase review focused on frontend foundations',
|
||
'Structural audit and prioritized roadmap',
|
||
'Component system extraction plan',
|
||
'CSS cleanup and token strategy',
|
||
'Accessibility baseline',
|
||
],
|
||
},
|
||
{
|
||
heading: 'Hands-On Implementation (optional)',
|
||
bullets: [
|
||
'Direct refactoring and component system creation',
|
||
'Tokenized design system rollout',
|
||
'Pairing with your engineers',
|
||
'Documentation and knowledge transfer',
|
||
],
|
||
},
|
||
{
|
||
heading: 'Ongoing Advisory (optional)',
|
||
bullets: [
|
||
'Periodic architecture reviews',
|
||
'Guardrails as you scale',
|
||
'Guidance on feature/system tradeoffs',
|
||
],
|
||
},
|
||
],
|
||
},
|
||
],
|
||
who: {
|
||
whoForHeading: 'Ideal fit',
|
||
whoForList: [
|
||
'Founder-led SaaS teams',
|
||
'1–10 engineers',
|
||
'Recently launched MVP',
|
||
'Feeling UI friction or code fragility',
|
||
'Want adult-level architecture without slowing down',
|
||
],
|
||
whoNotList: [
|
||
'Teams who only want features shipped as fast as possible without regard for structure',
|
||
'Organizations looking purely for architecture slide decks',
|
||
'Large enterprises needing formal procurement processes',
|
||
],
|
||
},
|
||
scheduleCta: {
|
||
sectionId: 'final-cta',
|
||
headingId: 'final-cta-heading',
|
||
title: 'Ready to stabilize your MVP?',
|
||
subtitle:
|
||
"If your MVP shipped fast but now feels fragile, let's reinforce the foundation before iteration slows further.",
|
||
bookingLinkTitle: 'Schedule a discovery call',
|
||
bookingLinkUrl: `${discoveryCallUrl}-schedule-section`,
|
||
showEmailLink: true,
|
||
},
|
||
meta: {
|
||
title: 'MVP Architecture & Launch Consultant | mifi Ventures',
|
||
description:
|
||
'I help early-stage SaaS teams build and stabilize MVPs with clean frontend foundations, reusable components, and scalable architecture—so you can ship fast without creating chaos six months later.',
|
||
jsonLdServiceDescription:
|
||
'MVP architecture and launch for early-stage SaaS: clean foundations, reusable components, tokenized design systems, and accessibility from day one. Fixed-scope engagement, hands-on implementation, and optional advisory.',
|
||
},
|
||
};
|