I’m Rajesh, a frontend engineer in Kolkata. Studios, agencies and brands send me their designs, and I build them to the pixel: every state accounted for, the motion as drawn, and pages that stay quick on a slow phone.

Measuring this page in your browser…

Agascendercap heightx-heightbaselinedescender
Eczar 800, set by Rosetta. Each line is the font’s own metric, measured in your browser just now. Try the type

These are loose. Drag one.

Feed it the real world.

Figma gets the perfect name. Real users bring everything else. Drop something awkward on the built card and watch it hold, then try the same snack on a build made from the happy path.

Tune it. The code writes itself.

Every visual decision becomes a named token, so a rebrand is a handful of values, not a rewrite. Pick a type pairing while you are here.

Everything in the file, and the parts that aren’t.

  • Desktop, tablet and phone from one Figma
  • Every hover, empty, loading and error state
  • Motion and page transitions as drawn
  • A CMS your client can’t break
  • A speed budget we agree on and measure
  • Accessibility that passes an audit
  • WebGL and 3D when it earns its place
  • A handover your next developer will thank you for

How it works.

Four steps. Each one ends with something you keep.

  1. A call, then a written scope

    We walk through the file together. You get a one-page plan: what gets built, what “done” means, the risks, and a written quote.

    You keep: the plan.

  2. A first milestone

    A small, real piece of the build, early, so you can judge the work before the rest of it.

    You keep: working code.

  3. Built in the open

    A preview link that grows with the build. Every claim that something works comes with the check behind it.

    You keep: a running build.

  4. Handed over properly

    Code, documentation and accounts in your name. Your next developer can pick it up cold.

    You keep: everything.

One honest line. Making the build match the agreed design is part of the job until launch. A new design halfway through is new work, and we agree it before I start.

You talk to the person who builds it.

No account manager and no hand-off to someone junior. The person who answers your message is the person writing the code. I work on India time and keep evening hours for studios in Europe and the Americas.

Need a break? Five things in a tiny town are a pixel or three off. Forty seconds to find them.

Do you do…?

Start with a sentence.

Whatever you tried on this page is already listed. Change anything, then copy it.