Stack Selection Workshop
Astro, Next.js, React, or something smaller? We map SEO needs, editor workflows, app depth, and team skills to a recommendation you can defend to investors.
// frontend.consulting_services()
Available for hireNot every problem needs a six-month build contract. Sometimes you need a senior frontend opinion — which framework, what to fix first, whether your agency quote is sane, or how to unblock the team before the next funding milestone. That is what consulting is for.
Short engagements with clear outputs — so you make better decisions before signing a large development SOW.
Astro, Next.js, React, or something smaller? We map SEO needs, editor workflows, app depth, and team skills to a recommendation you can defend to investors.
Folder structure, state boundaries, design system maturity, and API coupling — with a prioritized refactor list ranked by risk vs reward.
Lighthouse, field data, bundle analysis, and third-party script review — fixes grouped into quick wins vs structural work.
Second opinion on proposals, timelines, and technical scope before you sign — especially when you are non-technical and the jargon is thick.
Founders and leads book consulting when the path forward is unclear or expensive guesses are on the table.
Twitter says Next, your dev says Remix, marketing wants Webflow. I cut through noise with criteria tied to your actual product.
Agencies blame hosting, devs blame design assets. An audit assigns fixes to layers with effort estimates.
I quantify tech debt and migration risk so you do not torch a workable codebase — or pretend patches will fix a dead stack.
Job posts that ask for 'React ninja' attract mismatches. I help define the first 90 days and interview signals.
Tight scopes, written outputs, optional follow-on implementation only if you want it.
Goals, constraints, access needs, and which decisions must be unblocked this month.
Repo, analytics, Search Console, Figma, or vendor docs — whatever matches the engagement type.
Written summary with prioritized actions, effort bands, and what to ignore for now.
60–90 minute walkthrough with your team — Q&A, tradeoffs, and optional implementation quote.
// hire.now()
Describe the decision you are stuck on — stack, audit, or agency scope. I will suggest a consulting format, timeline, and fixed fee range.
Start a ProjectBreadth from production work — recommendations grounded in what I actually ship.
Representative systems I review — the same patterns that show up in audit engagements.
High-frequency React UI — consulting clients with live data products learn from patterns like WebSocket schemas, render budgeting, and state isolation used here.
Astro + TypeScript marketing site — a concrete example when consulting clients debate whether they need Next.js complexity or a lean content stack.
No. Many engagements end with a report and your team executes. I offer implementation only when you want continuity — never as a requirement.
Prioritized findings: LCP/INP drivers, bundle and image issues, third-party scripts, and caching gaps — with effort estimates and what to defer.
Yes. Second opinions on scope, acceptance criteria, and technical reviews are common. I stay constructive — the goal is your outcome, not agency drama.
Stack workshops often fit in 1–2 weeks with async prep. Deeper architecture reviews may take 2–4 weeks depending on repo size and stakeholder count.
Yes. Audits often touch unreleased product plans and vendor contracts. Standard NDAs are fine.
// contact.init()
// status.check()
Available for freelance — US/UK/EU clients preferred.
Full projects, hourly, and retainers welcome.
// message.compose()
message.sent()
I'll respond within 24 hours.
Something went wrong. Please try again.
No spam · Project details stay confidential · NDA available on request