SPAs, Next.js apps, design systems, dashboards. No agency markup. Fixed monthly price. 14-day money-back.
- Scope
- Ship
- Iterate
monthly subscription
Who this is for
You are a funded founder or technical lead who needs a React product built properly — not handed off across three time zones to a rotating bench. You want one senior engineer who owns the product, speaks plainly about tradeoffs, and ships working software on a predictable schedule.
The pain today
- Agencies quote $150/hr blended rates and put a junior on your ticket.
- Freelance marketplaces hide seniority behind filtered profiles.
- Hourly billing inflates the moment scope shifts by a story.
- React codebases accumulate debt when nobody owns the architecture.
- You need a single name on the accountability line — not a Slack channel.
The outcome you get
- One senior React engineer across product, design, code, and deploy.
- Fixed $4,999/mo subscription — no hourly surprises, no scope-creep invoices.
- 2–4 day delivery cycles with daily async updates.
- TypeScript by default, tested to critical-path depth, production-ready from day one.
- Work Made for Hire — every commit is yours from the moment it lands.
What React work actually gets built
I build React SPAs using Vite or Next.js as the host, Next.js applications with App Router and Server Components, design-system foundations (shadcn/ui, Radix, Tailwind, token layers), authenticated dashboards, marketing sites with heavy React interactivity, embedded widgets, chat interfaces, and performance-critical UIs like real estate search portals and broadcast control panels.
State management follows the data shape: React Query or SWR for server state, Zustand for global client state when Redux would be overkill. React 18 concurrent features — transitions, Suspense, deferred values — get used when they solve a real problem, not because they exist. I do not reach for a pattern until the pain that warrants it shows up.
What is out of scope: React Native, Electron, embedded systems, and WebGL-heavy experiences. Those are different disciplines. I will name a specialist if the work points that direction.
One senior React engineer across product, design, code, and deploy.
Real work: Imohub and bolttech
Imohub is a Brazilian real estate portal I rebuilt from the ground up as CTO. The stack was React plus Next.js plus Laravel plus MongoDB plus Meilisearch on AWS. The result: 120k+ properties indexed, sub-0.5-second query response, roughly 70% infrastructure cost reduction, and top-3 Google rankings. The React layer handled an unusually demanding combination of SSR for SEO, client-side search with near-instant results, and a property-detail experience that needed to feel fast on mobile.
At bolttech, a $1B+ fintech unicorn, the React front end was the customer-facing surface for a payment orchestration platform spanning 40+ providers across Asia and Europe. That project required React component architecture that stayed coherent across multiple product teams and stayed performant under real transaction load. Zero post-launch critical bugs.
120k+: Properties indexed and searchable.
Timeline expectations by project type
Discovery week is a paid engagement. It produces a written spec, an architecture decision record, and a delivery schedule with milestones.
Typical timelines from discovery kickoff: a landing page with auth and a simple dashboard takes 2–3 weeks. A mid-size marketing site with a headless CMS takes 3–5 weeks. A SaaS dashboard with auth, role-based access, and Stripe payments takes 6–10 weeks. A mid-to-large React SPA with multi-tenant logic or a complex data model runs 10–16 weeks.
Those ranges are real, not marketing copy. They assume daily async updates and a weekly 30-minute sync. Scope changes get repriced in days, not in a change-order negotiation.
React in 2026: what a senior engineer actually handles differently
React 19 and the App Router matured the framework considerably. Server Components shift data-fetching concerns to the server without a separate API layer, which reduces client bundle size and speeds up First Contentful Paint on content-heavy pages. I have used this pattern on production Next.js builds.
Typescript is the baseline on every new project, not a bolt-on. Vitest or Jest covers unit logic; React Testing Library covers component contracts; Playwright covers the critical-path end-to-end flows. Test coverage targets what breaks in production, not a vanity percentage.
Core Web Vitals matter commercially. Lighthouse scores in the 90s are achievable on most React applications with the right architecture choices upfront — code splitting, image optimization, font loading strategy, and not shipping 400kb of JavaScript on first paint. I have seen agencies deliver React builds that score in the 40s. That is a business problem, not just a technical one.
How pricing works
The subscription is $4,999/mo flat. No hourly billing, no scope-creep invoices. The 14-day money-back guarantee is a full refund if you are not satisfied inside the first two weeks — no conditions, no questions. After that, cancel anytime on a monthly basis.
I keep one customer at a time by design. That constraint is not a marketing line — it is how I maintain response times under 24 hours and keep delivery cycles at 2–4 days. Work Made for Hire means every commit is contractually yours. Post-launch fixes are covered under the standard policy: if it ships, it works.
Recent proof
A comparable engagement, delivered and documented.
Rebuilt a real estate portal at a fraction of the cost
Rebuilt Imóveis SC's real estate portal as ImoHub, a faster, more scalable successor, handling 120k+ properties with sub-second search and drastically reduced AWS costs.
Read the case studyFrequently asked questions
The questions prospects ask before they book.
The flat rate is $4,999/mo with no hourly component. Agencies typically charge $75–$150/hr blended, which on a 10-week SaaS build puts total cost well above $30k — before revisions. The more meaningful difference is that agencies bill a blended rate and assign junior engineers to execution. With me, the senior engineer doing the estimate is the same person writing the code.
Both. I take on rescues, targeted refactors, feature additions on existing apps, and greenfield builds. The monthly rate is the same either way. Existing codebases get a one-week audit before development begins, so I can tell you exactly what the debt looks like and what it will take to clear it.
React 18 or 19 depending on the project's stability requirements. Next.js with App Router for SSR and Server Component patterns. TypeScript on every project, no exceptions. Vite for pure SPA builds where SSR is not needed. State management follows the data shape — React Query for server state, Zustand for customer-global state when warranted.
It depends on scope. A landing page with auth: 2–3 weeks. A SaaS dashboard with auth and payments: 6–10 weeks. A mid-to-large SPA with multi-tenant logic: 10–16 weeks. The discovery week produces a written schedule with milestones, so you have real numbers before development starts — not a range I adjust after the first sprint.
Yes. Vitest or Jest for unit tests, React Testing Library for component contracts, Playwright for end-to-end coverage on critical flows. I target test coverage at paths that break in production — auth, payments, data writes. A 100% coverage number that misses those paths is not useful. The goal is confidence, not a metric.
Both. I set up design-system foundations using shadcn/ui, Radix primitives, and Tailwind with a token layer when a project needs one. I also take Figma handoffs and work directly with designers — design reviews, component critiques, implementation that matches the spec. Some of the more polish-heavy interfaces I have shipped started from detailed Figma files.