HimanshuRawat
00 · Services1 slot · Q3 2026

Three product problems I can help move forward.

The strongest fit is work that needs product judgment, interaction decisions, and frontend implementation to stay close. Choose the problem that resembles yours; the exact scope comes after we review the workflow and evidence together.

1 slot · Q3 2026Usually replies within 24 hoursAsync-friendly · UTC+5:30
01
Focused

Ship a Focused Product Surface

Turn one clear product problem into a reviewable, production-ready interface.

For Teams with a defined workflow or screen that needs product clarification, interaction decisions, and frontend implementation.

  • A written workflow and edge-case review
  • React or Next.js implementation in TypeScript
  • Responsive, keyboard, loading, empty, and error states
  • Reusable components for repeated interface patterns
  • Reviewable deployment and implementation notes
Last 3 Feet · shipped in five days with Lighthouse 98
Timeline
5 to 7 days
Engagement
Fixed price
Pricing
Quoted after scope review
Stack
Next.jsTypeScriptTailwindVercel
02
ProductCommon scope

Build or Improve a Product Workflow

Shape and ship a frontend-heavy workflow without separating product, interaction, and implementation decisions.

For Founders and product teams working on an MVP, onboarding flow, dashboard, internal tool, or a substantial feature in an existing product.

  • Problem framing and a scoped first release
  • User flows and interaction decisions where the brief has gaps
  • React and Next.js frontend with reusable component patterns
  • Supporting APIs, authentication, and data work where required
  • Regular walkthroughs with decisions documented in the repository
  • Handoff notes for the next product and engineering work
CVLeap AI · working product built in eight weeks
Timeline
4 to 10 weeks
Engagement
Fixed scope or weekly retainer
Pricing
Scope and price agreed before work starts
Stack
Next.jsTypeScriptMongoDBSupabaseStripe
03
Applied AI

Add an AI-Assisted Workflow

Use AI inside a specific task where it can reduce manual work or make a workflow easier to complete.

For Product teams testing voice interaction, drafting, summarization, retrieval, or structured automation inside an existing user workflow.

  • A concrete user task and a non-AI fallback path
  • Prototype and technical feasibility review before a larger build
  • Prompt, tool-calling, and structured-output implementation as needed
  • Latency, failure, cost, and human-review behavior documented
  • A product interface around the AI behavior, not a generic chatbot shell
  • Measurement hooks for reviewing usefulness after release
Phone Assistant · measured voice-support demo
Timeline
6 to 12 weeks
Engagement
Fixed scope with milestones, or weekly retainer
Pricing
Quoted after the discovery call
Stack
OpenAI RealtimeClaudeVercel AISupabasePostgres
01 · Always included

The working agreements that keep scope, decisions, and handoff clear.

  • A written scope with assumptions, deliverables, timeline, and price
  • TypeScript for the product code I own
  • Reviewable work and regular walkthroughs of the working product
  • Responsive behavior and accessibility considered in the implementation
  • Reusable patterns documented when future features depend on them
  • Code and project artifacts handed over at the end of the engagement
02 · How we'd work

From product problem to a reviewable build.

  1. 01

    30-minute call

    We discuss the product problem, the current state, and what needs to change. If I am not a good fit, I will say so.

  2. 02

    Scope the useful slice

    I turn the discussion into a written scope with the workflow, deliverables, assumptions, timeline, and price. Larger ideas are split into a first version that can be reviewed or tested.

  3. 03

    Build in visible increments

    Work moves through reviewable pull requests and regular walkthroughs. Product and interaction decisions stay visible alongside the code.

  4. 04

    Hand over the reasoning

    You receive the code, the reusable patterns, and documentation for decisions that future product or engineering work depends on.

Not sure which tier fits?

Describe the product, the workflow, and what currently causes friction. I will suggest a sensible first scope and explain what information is still missing before I can price it.

Next step

Bring the workflow, not a polished brief.

A rough description is enough. We can use the first call to identify the user problem, the product constraint, and the smallest useful piece of work.

Book a 30-min call
1 slot · Q3 2026Usually replies within 24 hoursAsync-friendly · UTC+5:30