Koustav Ganguly
Full-Stack Developer & Technical Writer
Available for projects
Ship landing pages and frontend work faster — milestones, clear scope, payments that match.
React / Next.js UI from Figma, with written scope so you know what ships next.
Featured work
Tap to open live projects
A bit more context
3+ years shipping production UI — marketing sites to internal tools — with maintainable React / Next.js.
Remote: Figma → responsive code; handoff docs so your team owns the stack after launch.
Typical outcomes
Plain-language before → after — real screenshots when NDAs allow; this is the shape of how engagements land.
Situation
Site feels dated; main CTA isn’t converting.
Outcome
Responsive hero + lead flow in two milestones — scope and dates fixed up front.
Situation
Figma looks good; production breaks on mobile.
Outcome
React / Next.js that matches design, with a handoff your team can extend.
What you get when we work together
Milestones you can plan around
Phased work with dates and deliverables in plain language — no vague “almost done.”
Frontend + design, end to end
Landing pages to product UI: responsive React / Next.js from your Figma (or similar) handoff.
Scope and payments that match the work
Written scope before build; deposit + milestone payments tied to what actually ships.
Focused engagements: async-friendly updates, no bloated retainers, and no meetings that exist only to schedule more meetings.
How it works
Brief & alignment
Call or brief: goals, stack, timeline, and what “done” means — same problem, same scope.
Milestone plan
Written phases, deliverables, and cost per milestone — adjust before build, not mid-flight.
Ship & handoff
Build to scope, demos at milestones, then repo + notes so you can run with it.
Scope at a glance
What I need from you
- Goals, audience, brand constraints
- Figma, references, or links to what we’re fixing
- Timeline + budget band (rough is fine)
What you receive
- Scope + milestone plan before major build
- Production frontend to the agreed deliverables
- Payments tied to milestones — see pricing anchors; full quote after alignment
15 minutes to see if we’re a fit — no pitch deck required.
Pricing anchors & scope →Who this is for
Good fit
- Teams or founders who want landing pages or frontend work shipped on a defined timeline with written scope
- Projects where design handoff → responsive, production-ready UI is the core
- Clients who are serious about milestones and structured payments for larger engagements
- When the offer is right — including full-time roles — I’m open to a longer commitment if compensation and fit make sense
Not a fit
- “Just see what you can do” with no budget, scope, or time for a short discovery step
- Expecting unlimited revisions or daily direction changes without adjusting scope or timeline
- Pure backend-only or legacy-only maintenance with no frontend or design component (not my focus)
FAQ
What happens after I book a call?+
We use the call to clarify goals, audience, stack, and timeline. If we’re a fit, you get a short written summary: suggested milestones, deliverables, and how pricing would work — before any build starts.
Are the numbers on the pricing page final?+
The public page shows honest anchors and how pricing works — not every line item. Final quotes, batch or package math, retainers, and overages are spelled out in writing after we align on scope (usually after the short call or via the pricing guide when you request it).
How do milestones and payments usually work?+
Smaller pieces may be a single payment; larger work is often split — for example a deposit to start, then payments tied to agreed milestones. Everything is documented before work begins.
Do you charge hourly or fixed price?+
Most client work is scoped as fixed milestones or fixed project fees so you know the cost up front for that scope. Hourly can make sense for small ad-hoc support — we’ll pick what fits your project.
What’s included in revision rounds?+
The pricing page summarizes what’s typical; your proposal spells out revision allowances for your scope. Tweaks within the agreed design are included; new features or direction changes may mean a small scope add-on — we’ll say so before doing the work.
Who owns the code and assets when we’re done?+
After final payment for the agreed scope, you receive the deliverables as defined in our agreement (e.g. repo access, handoff docs). Specifics are confirmed in writing for each project.
Can you work with my designer or existing Figma file?+
Yes. I regularly implement from Figma (or similar): components, responsive behavior, and interaction polish — and I’ll flag anything that affects timeline or scope early.
Do you sign an NDA?+
Yes — standard NDAs for client work are fine once we agree we’re a good mutual fit.
