blue pillthe story ends. you get a résumé.
red pillyou stay in wonderland

Sahil Badgewar

Web Designer | Hardworking | Passionate About Digital | Open To Opportunities | Humbled To Announce

Professional Summary

Dynamic and results-oriented digital professional with a proven track record of leveraging synergies to ideate best-in-class web experiences. I eat, sleep and breathe websites. Websites are my passion. My passion is websites. I once saw a website in a dream and woke up inspired to circle back on it.

Core Competencies

Experience

Webflow Developer — Various Companies
Made websites. The websites had a home page, and in most cases, additional pages. Ensured all buttons were clickable. When clients said "make the logo bigger," I made the logo bigger. Proactively circled back, touched base, and moved needles. Once fixed a bug by refreshing the page.

Key Achievements

Testimonials

"Sahil made our website. It has pages, and the pages have content on them."— A Satisfied Client
"He replied to my email."— Another Client
"Who?"— Industry Leader

Hobbies

Watching webinars. Networking (LinkedIn only). Thought leadership. Manifesting. Adding people I've never met and writing "Great connecting!"

You took the blue pill. This is the version of Sahil the algorithm wants you to believe in — buzzwords, vibes, and zero substance.

The real one rebuilt a marketing team's entire publishing system so they never file a dev ticket again. Wired a fintech consent SDK into Webflow when the docs said it needed React. Turned a 3-person webinar operation into a form submission.

None of that fits in a bullet point that starts with "Passionate about."

wake up. take the red pill →
⚠ CONNECTION INTERCEPTED
// you followed the white rabbit
Most visitors never catch it. You did.

operator's note #7: the best CMS structure I ever shipped had zero custom code on the page. all the intelligence lived in the data model. that's the whole trick — move the complexity to where it can't break.

hidden commands for the terminal below: wake up redpill sudo ls the matrix

and one more thing — mention "white rabbit" in your email and I'll know you went deep enough to find this. those emails get answered first.
sahil_badgewar // operator
trace: 00:00:00
// transmission from: somewhere between India & the Internet

Most websites live
in the Matrix.
I see the code.

Most websites are assembled. Some are designed. I build the third kind — the ones that behave like products, respond like systems, and keep working long after the launch post. Webflow on the surface. Something else underneath.

█ enter the construct
scroll — or click the rain. it listens.
01 // incoming signal

I don't start with layouts.
I start with constraints.

Over the past few years, I've worked inside SaaS teams where speed matters, marketing moves fast, and "just one more page" never really ends.

That's where most Webflow builds break — not visually, but structurally. The CMS wasn't modeled for growth. The integrations were glued on. The page that worked in the demo starts falling over by month three. A glitch in the build, dismissed as déjà vu.

So I work on the parts you don't see at first glance: how content scales, how flows behave, how integrations don't fall apart at 2AM.

The goal isn't a site that looks good. It's a system that keeps working.

— end of transmission // signal verified
Webflowadvanced
CMS APIcustom
JavaScriptnative
GSAPmotion
Finsweetattributes
Wizedlogic
Memberstackauth
Xano / Airtablebackend
Segment / HubSpotdata
Zapier / Makeops
02 // anomalies resolved

Three glitches in the system
that needed an operator.

anomaly_01 :: marketing-cms-system sector: B2B SaaS RESOLVED

The marketing system that didn't need me anymore.

Glitch
Marketing wanted 3 landing pages a week. Dev was the bottleneck. Every page meant a ticket, a review, a deploy.
Rewrite
Built a modular CMS structure where components were configured, not coded. Collections drove page variants, SEO, and tracking.
Output
Team ships pages without touching code. Not faster pages — fewer bottlenecks.
CMSComponentsFinsweetSEO
dev dependency: removed
anomaly_02 :: consent-sdk-integration sector: Fintech RESOLVED

The consent flow that respected the flow.

Glitch
A third-party SDK had to fire at exactly the right moment. Too early, users bounced. Too late, compliance broke. Docs assumed React — we were on Webflow.
Rewrite
Wired the SDK into Webflow's page lifecycle with custom JS, scroll and intent triggers, and a fallback path. The challenge wasn't technical — it was timing.
Output
Consent rates up. No banner blindness. No compliance escalations.
SDKCustom JSCompliance
UX preserved // compliance met
anomaly_03 :: webinar-automation sector: SaaS / Ops RESOLVED

The webinar system that removed operations.

Glitch
Every webinar meant manual CSV exports, CRM tagging, Slack handoffs, and a calendar invite someone always forgot.
Rewrite
Form input mapped straight to backend systems — CRM, email, calendar, Slack — triggered from the Webflow form itself. No manual steps. Just outcomes.
Output
A webinar takes one person now, not three. The page became the operator.
WebhooksMakeHubSpotSlack API
3 people → 1 person
03 // rules of the construct

Some rules can be bent.
These don't break.

RULE_01

There is no "just a page".

Every page is part of a system. If it can't scale, it's already broken — you just haven't hit the load yet.

RULE_02

Reality over polish.

I'd rather ship something that works under pressure than something that only looks good in a case study. Edge cases are where the work lives.

RULE_03

Integration is the real work.

The UI is easy. Making it talk to the rest of the stack — CRM, analytics, auth, backend — that's where most Webflow builds quietly fail.

RULE_04

Async is the default.

Timezones aren't the problem — unclear thinking is. Clear briefs, written decisions, Looms over meetings.

// live uplink — type a command. or don't. the construct decides.
operator@construct: ~ tty1 // encrypted
> [enter]
04 // exit the matrix

The phone is ringing.
Answer it.

If you're building something that needs to hold up — send a Loom, a paragraph, or a link. I'll tell you if it's a fit within 48 hours. If it isn't, I'll tell you who to talk to instead.

█ hello@sahilbadgewar.design book a 20-min call ↗
☎  currently replying within 48h // IST // capacity: 1 project
🐇 follow the white rabbit
déjà vu — a glitch in the matrix. they changed something.