}
);
}
/* ---------------- Conversion band (reused on every page) ---------------- */
function CTABand({
title, // white lead of the headline
body, // muted trail of the headline
cta = "Start your project",
href = "Contact.html",
// accepted for backward-compatible call sites; not rendered in this layout
eyebrow, tone, actions
}) {
const lead = title || "Built for teams that need complex software made clear,";
const trail = body || "trusted quickly, and easy to live with as it scales.";
return (
{/* atmospheric glow in the project tone */}
{/* faux app chrome strip */}
{[0, 1, 2].map((i) => )}
{/* abstract content lines */}
{/* label */}
{!hideLabel &&
{project.industry}
{project.name}
}
);
}
/* ---------------- CONTENT DATA ---------------- */
const STATS = [
{ value: "14+", label: "Years designing products" },
{ value: "10+", label: "Products shipped to production" },
{ value: "5+", label: "Design systems built from scratch" },
{ value: "180+", label: "Countries reached at scale" }];
const PROJECTS = [
{
id: "sentinel", name: "Reimagining Reporting", thumb: "site/reporting-dashboard-thumb.jpg", longform: "reporting", industry: "Power BI · Design Strategy", year: "2026", tone: "violet",
role: "Lead Product Designer", duration: "2023–2026", team: "Dashboard branding · Design system", teamLabel: "Scope",
metric: "", metricLabel: "",
disciplines: ["Product Design", "Design Systems", "Enterprise UX"],
summary: "The organization is migrating dashboards from Qlik to Power BI to modernize its analytics and user experience.",
challenge: "The organization was migrating a large suite of dashboards from Qlik to Power BI. Each report had its own layout, chart formatting, and visual style, and the tool's limited customization meant every design decision had to be feasible for developers to build. The brief was to bring consistency, brand alignment, and a scalable reporting standard to the whole ecosystem.",
process: [
"Audited the existing dashboards and defined a reusable Power BI theme, brand-aligned palette, and standardized layouts.",
"Built a shared style guide and component library so designers and developers worked from one foundation.",
"Created a low-fidelity wireframe kit to keep early conversations focused on structure and flow.",
"Published templates, themes, and how-to guides to a central hub to drive adoption across teams."],
deliverables: ["Power BI theme & template", "Reporting design system", "Wireframe kit", "Dashboard guidelines", "Adoption toolkit & docs"],
impact: ["One consistent reporting standard across products", "Faster dashboard creation from reusable templates", "Brand-aligned, legible data visualization", "A scalable framework the teams could extend"],
lessons: "Designing within a tool's real constraints is the job. The wins came from building a shared foundation teams could reuse, not from perfecting any single dashboard."
},
{
id: "ledgerline", name: "One System, Infinite Scale", thumb: "site/design-system-thumb.png", banner: "site/design-system-banner.png", longform: "ds", industry: "Healthcare · Design System", year: "2024 - 2026", tone: "blue",
role: "Product Design Lead", duration: "Ongoing", team: "1 Engineer",
metric: "", metricLabel: "",
disciplines: ["Design Systems", "Interface Direction", "Design–Dev Collaboration"],
summary: "A scalable healthcare design system enabling faster design, consistent experiences, and seamless design–development collaboration.",
challenge: "A fragmented legacy framework had left teams building their own components and applying styles inconsistently, causing design drift, duplicated effort, and slower delivery. The brief was to transform it into a scalable, brand-aligned design system on a tight timeline — one solid enough to support multiple products and future multi-brand expansion.",
process: [
"Established a three-tier token architecture (brand, alias, mapped) for color, type, and spacing.",
"Prioritized 50+ core components using an atoms → molecules → organisms methodology.",
"Aligned every component with development through Storybook so design and code stayed in sync.",
"Ran onboarding workshops and gathered feedback to drive adoption and keep the system lean."],
deliverables: ["Three-tier token system", "50+ component library", "Storybook integration", "Design guidelines & docs", "Onboarding & governance"],
impact: ["2× faster project turnaround", "Consistent output across teams and modules", "Duplication eliminated with shared components", "A scalable foundation for multi-brand growth"],
lessons: "A design system is a living product, not a component library. Strong governance keeps it sustainable; too much flexibility just recreates the complexity you set out to remove."
},
{
id: "atlas", name: "Reinventing Risk & Compliance", thumb: "site/risk-compliance-thumb.png", thumbScale: 1.4, longform: "atlas", industry: "Design Systems · Platform", year: "2021 - 2023", tone: "orange",
role: "Design Systems Lead", duration: "2 Years 4 months", team: "Systems team of 3",
metric: "3× faster", metricLabel: "Time from design to shipped UI",
disciplines: ["Design Systems", "Design Leadership", "Governance"],
summary: "Transforming legacy workflows into a modern, intuitive experience. Built for clarity, efficiency, and scalability.",
challenge: "A feature-rich GRC platform relied on a one-size-fits-all dashboard that ignored the distinct needs of each persona. Years of developer-led additions had left deep navigation, inconsistent patterns, and workflows that pushed users to spreadsheets and workarounds. The challenge was accumulated UX debt, not missing capability.",
process: [
"Ran a comprehensive UX audit — session recordings, support tickets, stakeholder and user interviews.",
"Restructured the information architecture around role-based experiences for each persona.",
"Streamlined core workflows, cutting incident registration from three steps to one.",
"Built a scalable, token-based design system with Storybook integration and UX governance."],
deliverables: ["UX audit & research report", "Role-based IA", "Streamlined incident & risk flows", "Decision-centric dashboards", "Design system & governance"],
impact: ["Risk & incident resolution from 15 min to 5 min", "66.7% reduction in registration effort", "Role-based dashboards for real-time visibility", "A scalable foundation for future enhancements"],
lessons: "Great enterprise design makes complex systems feel intuitive. Simplifying intricate workflows without losing functionality mattered more than any single new screen."
},
{
id: "northwind", name: "Transforming the Payroll Experience", thumb: "site/payroll-app-thumb.jpg", longform: "northwind", industry: "HR Tech · Payroll", year: "2021", tone: "coral",
role: "Senior UX Designer", duration: "2020 — 2021", team: "2 designers",
metric: "8.07 / 10", metricLabel: "Avg. first-round test rating",
disciplines: ["Product Design", "Complex Workflows", "Enterprise UX"],
summary: "A UX redesign that unifies payroll modules into a modern, intuitive, and efficient platform.",
challenge: "The payroll platform had grown into disconnected modules, each with its own patterns, leaving users to navigate dense, unintuitive workflows for everyday tasks. The brief was to unify the modules into one modern, efficient experience without disrupting the people who relied on it daily.",
process: [
"Audited the existing modules and mapped where users hit friction and dropped to workarounds.",
"Unified the experience around consistent patterns and a clearer information architecture.",
"Made timesheets and payroll data legible with clearer hierarchy and terminology.",
"Validated the redesign through moderated usability testing and iterated on feedback."],
deliverables: ["Unified payroll experience", "Consistent module patterns", "Legible timesheet views", "Usability-tested prototype"],
impact: ["8.07 / 10 average first-round test rating", "Everyday tasks made faster and clearer", "Consistent experience across modules", "A modern foundation for the platform to grow"],
lessons: "Unifying a fragmented product is mostly about restoring consistency. When patterns repeat, users stop relearning the interface and start trusting it."
},
{
id: "meridian", name: "Learn through cooking", thumb: "site/cooking-app-thumb.jpg", longform: "cooking", industry: "EdTech · iPad App", year: "2020-2021", tone: "magenta",
role: "Senior UX Designer", duration: "Jul 2020 - Mar 2021", team: "2 Designers",
metric: "100%", metricLabel: "Recipe-flow completion in testing",
disciplines: ["Product Design", "UX Research", "EdTech"],
summary: "A gamified application that helps teach STEAM (science, technology, engineering and arts), through healthy cooking and dynamic technology.",
challenge: "An iPad learning platform taught STEAM through cooking, but poor UX planning made it hard to use — a survey found 60% of students couldn't follow the existing design, steps were too long, and lessons carried a heavy cognitive load. The brief was a research-grounded redesign and rebrand that made learning feel magical.",
process: [
"Evaluated the existing app and ran 1-on-1 interviews with students, a teacher, and a parent.",
"Built a persona and mapped the recipe-cooking task flow end to end.",
"Restructured the information architecture and designed low- then high-fidelity prototypes.",
"Usability-tested the prototype with five users and folded findings into the next iteration."],
deliverables: ["UX research & persona", "Information architecture", "Recipe task flow", "Low- & hi-fi prototypes", "Rebranded iPad experience"],
impact: ["100% recipe-flow completion in testing", "Engaging, assessment-driven cooking lessons", "Clearer, more accessible learning steps", "A foundation targeting +25% signups, +50% school registrations"],
lessons: "Designing for kids rewards clarity over cleverness. Grounding every decision in research kept the experience genuinely usable, not just playful."
}];
const SERVICES = [
{
n: "01", name: "Product Design", tags: ["End-to-end", "0→1 & scale"],
blurb: "End-to-end product design for complex software — from early strategy and user flows to polished, shipped interfaces. I turn tangled workflows into products teams actually want to use.",
problem: "Complex products that have outgrown their original design and now confuse the people who depend on them.",
value: "Strategy-through-execution design that turns tangled workflows into products teams actually want to use — shipped, not just shown.",
client: "Founders and product leaders building serious software in regulated or complex domains."
},
{
n: "02", name: "Design Systems", tags: ["Tokens-first", "Governance"],
blurb: "Scalable, tokens-first design systems with the governance to keep them alive — so multiple teams ship consistently, accessibly, and far faster than before.",
problem: "Multiple products drifting apart, teams rebuilding the same components, brand and accessibility slipping.",
value: "A scalable, governed system — tokens, components, and the operating model to keep it alive — so teams ship consistently and faster.",
client: "Scaling orgs with several products and no single source of truth."
},
{
n: "03", name: "Interface Direction", tags: ["UX vision", "Leadership"],
blurb: "Experience direction and design leadership that set a clear UX vision and raise the craft bar across every surface of the product.",
problem: "A product with no coherent point of view — every screen a different opinion, no one steering the experience.",
value: "Experience direction and design leadership that set a clear vision and raise the bar across every surface.",
client: "Teams that need senior craft and direction without a full-time hire."
},
{
n: "04", name: "Brand Identity", tags: ["Digital-first", "Systems"],
blurb: "Digital-first brand systems that hold together from the marketing site to the deepest admin screen — one coherent experience, end to end.",
problem: "A brand that looks one way in marketing and another inside the product, eroding trust at every touchpoint.",
value: "Digital-first brand systems that hold together from the homepage to the deepest admin screen.",
client: "Companies whose brand and product experience have fallen out of sync."
},
{
n: "05", name: "Advisory & Audits", tags: ["Reviews", "Strategy"],
blurb: "UX audits, design reviews, and maturity assessments that turn a vague 'something's off' into a ranked, actionable roadmap you can move on.",
problem: "A nagging sense the experience is holding growth back — but no clear, prioritized plan to fix it.",
value: "UX audits, design reviews, and maturity assessments that turn a vague concern into a ranked, actionable roadmap.",
client: "Leaders who need an expert outside read before committing budget."
}];
const PRINCIPLES = [
{ n: "01", title: "Start with the real workflow", body: "Not the one in the docs. I shadow the people who'll use the product until I understand the job they're actually doing — then design for that." },
{ n: "02", title: "Make complexity legible", body: "Enterprise software is complex for real reasons. The work isn't to hide that — it's to make it understandable, so people can act with confidence." },
{ n: "03", title: "Design the system, not the screen", body: "One good screen is a sketch. A system of decisions — tokens, patterns, principles — is what scales across products and survives the next feature." },
{ n: "04", title: "Tie design to business outcomes", body: "Beautiful that doesn't move a number is decoration. I design toward the metric that matters and measure whether it moved." }];
const TESTIMONIALS = [
{ quote: "Martin doesn't just design screens — he reframes the problem. He cut our audit prep from weeks to days and changed how the whole team thinks about the product.", name: "Priya Nair", role: "VP Product, Sentinel" },
{ quote: "The most senior design thinking we've worked with. Martin built a system that's still the backbone of every product we ship two years later.", name: "Daniel Roth", role: "Head of Design, Atlas Platform" },
{ quote: "He made a deeply technical product feel obvious. Adoption quadrupled. I'd hire him again in a heartbeat.", name: "Mei Lin", role: "Founder & CEO, Meridian" }];
const CLIENT_LOGOS = [];
const FAQS = [
{ q: "What kinds of projects do you take on?", a: "Complex, high-stakes software — enterprise platforms, GRC and compliance tools, fintech, data products, and design systems. If the problem is genuinely hard and the stakes are real, it's interesting to me." },
{ q: "How do you usually engage?", a: "Three common shapes: a fixed-scope project (a redesign, a 0→1 product, a design system), an ongoing advisory retainer, or a focused audit. We'll pick the one that fits your moment on a first call." },
{ q: "Do you work with teams outside India?", a: "Yes — most of my work is with distributed teams across the US, Europe, and Asia. I'm based in Bangalore and overlap comfortably with most time zones." },
{ q: "What does a typical timeline look like?", a: "Audits run 2–3 weeks. Project engagements typically run 2–6 months depending on scope. I take on a small number at a time so each gets senior attention end to end." },
{ q: "Is there a minimum budget?", a: "Engagements start around the cost of a senior in-house designer for the period. But reach out regardless — if the problem is a fit, we'll find a sensible shape." },
{ q: "Can you work with our existing team?", a: "Almost always. I plug into your product, engineering, and design partners directly — raising the bar with the team, not around it." }];
/* ---------------- Scroll progress (pinned below nav) ---------------- */
function ScrollProgress() {
const [pct, setPct] = React.useState(0);
React.useEffect(() => {
const onScroll = () => {
const h = document.documentElement;
const max = h.scrollHeight - h.clientHeight;
setPct(max > 0 ? (h.scrollTop / max) * 100 : 0);
};
onScroll();
window.addEventListener("scroll", onScroll, { passive: true });
window.addEventListener("resize", onScroll);
return () => { window.removeEventListener("scroll", onScroll); window.removeEventListener("resize", onScroll); };
}, []);
return (