Skip to content

Both halves of the stack, one person.

Four things I do for clients, how an engagement runs, and the three ways to work together. Rates are quoted after a short discovery call, never guessed.

Services

01

Full-stack product builds

An MVP or a feature set, scoped, built and shipped end to end.

  • .NET API plus React or Next.js front-end
  • PostgreSQL or SQL Server
  • CI/CD to Azure, AWS or Vercel
02

.NET API and backend

Services that stay fast under real load and survive an audit.

  • ASP.NET Core Web API, EF Core
  • Query and architecture tuning
  • NUnit and Moq test coverage
03

React and Next.js front-ends

Interfaces that feel finished: fast, accessible, animated with intent.

  • App Router, Server Components
  • Design-system driven UI
  • GSAP motion, measured performance
04

UI/UX to code

From a Figma file or a rough sketch to a working, tested screen.

  • Flows and wireframes in Figma
  • Component libraries and tokens
  • Hand-off that developers can use

How an engagement runs

  1. 01

    Discover

    We talk through goals, users and constraints, then scope the smallest version that proves the idea out. You get a written plan with dates before anything starts.

  2. 02

    Design

    Flows, wireframes and a component plan in Figma, reviewed together. Data model and API shape are decided here too, so the build does not stall on them later.

  3. 03

    Build

    Working demos over static mockups, on a shared board so you always know what is next. Unit tests ship with each feature and CI runs on every push.

  4. 04

    Ship

    Deployed, documented and handed over with a short session so your team is not left guessing. A post-launch window covers fixes, with a retainer available after that.

Engagement models

Pick the shape that fits the work. The number comes after we have scoped it together.

Best for

Bug fixes, feature add-ons, and teams that already have a backlog.

Rate shared after a quick discovery call, based on scope.

  • Weekly time & progress summary
  • No minimum commitment
  • Pause or scale anytime

Best for

MVPs, a new feature set, a redesign, or a full rebuild.

Quoted after scoping — usually within 1-2 business days.

  • Written scope & milestone plan before work starts
  • Fixed price, agreed up front
  • One structured revision round per milestone

Best for

Ongoing feature work, maintenance, and being on-call for issues.

Capacity-limited — I keep a small number of retainer slots open.

  • Reserved hours every month
  • Priority response time
  • Month-to-month, cancel anytime

Who joins for bigger scopes

  • Divyansh Jain

    Senior Software Engineer

    5+ years shipping resilient microservices and APIs for fintech & insurance platforms — ex-Cognizant.

    • .NET Core
    • C#
    • ASP.NET
    • React
    • Azure
    • SQL Server
  • Siddharth Sharma

    .NET + React Full-Stack Engineer

    Building SaaS for US local governments at Catalis — full-stack from PostgreSQL to production on AWS.

    • ASP.NET Core
    • React
    • PostgreSQL
    • AWS
  • Ajit Hazari

    Senior Software Tester

    Catches what slips through — manual and automated coverage across web, API, and enterprise tooling.

    • Selenium
    • REST Assured
    • Postman
    • Playwright
    • Swagger
    • Azure DevOps
  • Manoj Maddheshiya

    Automation Test Engineer

    5 years automating away the repetitive parts of QA, now leaning into AI-assisted testing.

    • Playwright
    • Selenium
    • Java
    • TypeScript
    • REST Assured

Before you write

Anything from a single feature or bug-fix on an existing codebase to a full product built from scratch — web apps, internal tools, WordPress sites, and API-heavy backends. If it's mostly React/Next.js or .NET/C#, it's a good fit.

Depends on scope. A fixed-scope project gets a milestone plan with dates during the discovery call; hourly and retainer work runs on a weekly cadence. I'll always give you a real estimate before anything starts, not a guess.

Yes, happy to sign one before we get into specifics — especially useful if you're validating an idea you'd rather keep quiet for now.

Both. Most of my recent work (Catalis, MeridianLink) has been modernizing and extending large existing systems, not starting from a blank repo.

Every engagement includes a short post-launch support window by default. Past that, you can move to a monthly retainer if you want an ongoing extra pair of hands — see the Pricing section above.

Send a message through the contact form with a rough idea of scope — I usually reply within a day to set up a quick discovery call.