01/Developer highlights
A visual builder gets you a page. These are the habits that decide whether that page is still fast, findable and editable a year later.
Every build carries a Core Web Vitals budget from day one. Images are sized and lazy-loaded, fonts are subset and preloaded, and render-blocking third-party scripts get deferred or dropped.
Sections are built once as Webflow symbols or React components, then reused across pages. A change to the card lands everywhere instead of in twelve near-identical copies.
Semantic heading order, unique titles and descriptions per page, canonical tags, Open Graph images, an XML sitemap and JSON-LD schema, all wired before launch rather than after.
Keyboard paths, visible focus indicators, labelled inputs and AA contrast are checked while building. Modals trap focus, menus close on Escape, and nothing depends on hover alone.
REST endpoints, webhooks and CMS syncs wired with typed responses, sensible retries and real states for loading, empty and error, so the interface never lies about what happened.
Motion tied to intent: entrance reveals, state feedback and scroll cues. Everything honours prefers-reduced-motion and runs on transform and opacity so the first paint stays fast.
02/Services
Most engagements start as one of these and grow into another. Scope is written down before anything is built, so nobody is guessing what was included.
01
Figma files turned into a Webflow build a marketing team can actually run without calling a developer every week.
02
Production interfaces in JavaScript and TypeScript, for the work that outgrows what a visual builder can express.
03
A measured audit, a prioritised fix list, and the fixes themselves, rather than a PDF of recommendations.
04
The wiring between your site and the tools your team already lives in, built to fail loudly rather than silently.
03/Featured projects
Six of ten case studies. Each one opens with the constraint that made it difficult, not the screenshot that made it look easy.
Regional logistics carrier
A twelve-year-old brochure site rebuilt as a Webflow property the marketing team runs on its own.
Developer tooling startup
A documentation frontend with instant client-side search and keyboard navigation throughout.
Five-location dental group
Five location pages rebuilt from templates into pages that each rank in their own neighbourhood.
Engineering recruitment firm
A Webflow careers portal kept in sync with an applicant tracking system nobody wanted to replace.
B2B analytics platform
A marketing site with a CMS-driven changelog the product team updates without touching the design.
Internal platform team
Thirty-one components consolidated from four product surfaces that had each invented their own button.
04/Experience
The through-line is maintenance. Almost everything I do differently now, I do because I once had to live with the alternative.
2016 — 2018
Independent
Hand-coded sites for local businesses in HTML, CSS and jQuery, learning the hard way that a beautiful layout nobody can edit becomes a maintenance bill within a year.
2018 — 2020
Digital agency
Built marketing sites and campaign pages against fixed launch dates, working from design files that arrived late and changed often. Learned to structure markup so a last-minute redesign is a class change, not a rebuild.
2020 — 2022
Product studio
Moved client work onto Webflow and rebuilt how the studio approached it: a documented class system, reusable symbols, and CMS models designed around how a marketing team actually works rather than how the page happens to look.
2022 — 2024
Product team
Joined an in-house engineering team building customer-facing interfaces in React and TypeScript. Owned a design system consolidation, spent real time in code review, and learned what maintaining a codebase for two years actually costs.
2024 — Present
Working directly with clients
Now taking on a small number of builds at a time, usually where a marketing site needs engineering judgement: a Webflow property with real integrations, a performance recovery, or a frontend that has outgrown what a visual builder can express alone.
05/Tech stack
A short list on purpose. I would rather go deep on six things a client project genuinely needs than claim a logo wall of twenty.
Build the section once, use it everywhere. When the brand changes, you edit one component instead of hunting fourteen copies of the same layout across the site.
06/Testimonials
The measure I care about is whether a team still feels ownership of the site six months after I have gone.
We had been quoted a rebuild three times and every quote skipped the boring parts. Shreyas started with the redirect map and the content model, which is exactly why nothing broke when we launched. Our team publishes without asking anyone for help now.
He asked better questions about our API than we did. The docs rebuild landed on time, the search is genuinely fast, and he left us a component structure our own engineers could pick up without a handover call.
Our images are the whole business, so I expected the usual argument about file sizes. Instead he built a pipeline that keeps them looking right and still loads on site with barely any signal. Three years on, I have published every project myself.
07/FAQ
If yours is not here, ask it directly. A straight answer costs me an email and saves us both a discovery call.
It means the platform has assessed the work against its own standards, so you are not taking my word for it. In practice it matters less than what it implies: a documented class system, CMS collections modelled around how your team publishes, and a build your marketing people can edit without a developer standing behind them.
I build. I work best from a Figma file, whether that comes from your designer or one I bring in. If you have no design at all, I can lay out a structure and typography system that works, but you will get a stronger result pairing me with a designer than asking me to do both jobs at half strength.
A focused five to eight page site is usually three to five weeks from approved designs, including content modelling, responsive passes, an accessibility check and training. Sites with real integrations or a large CMS migration run longer. I would rather give you a range after seeing the scope than a number that gets revised twice.
That is the point of building it this way. Content lives in CMS collections with the fields your team actually needs, and the layout holds whether a heading is four words or fourteen. Handover includes a recorded walkthrough and written notes, so the person who joins next year is not stuck either.
That is usually where I add the most value. Custom JavaScript handles filtering, calculators, conditional forms and API-driven content inside the Webflow build. When a requirement outgrows the platform properly, I will say so and we discuss moving that piece into a coded frontend rather than fighting the tool.
Yes, and I prefer inheriting something real to starting from an empty folder. I read what is there first, match its conventions, and raise anything genuinely broken rather than quietly rewriting it. If a refactor is warranted, it comes with reasoning and a migration path, not a rewrite dropped on your team.
Launch is when the numbers start mattering. Every build ships with Search Console verified, an XML sitemap submitted, structured data validated and a Core Web Vitals baseline recorded. I offer a check-in at thirty and ninety days to catch regressions, which are usually caused by a plugin or tracking script added after I left.
Taking on two new builds per month
Tell me the scope, the deadline and what has gone wrong before. You will get a straight answer on whether I am the right person for it, usually within a business day.