0 → 1, then make it scale

I build software that turns messy problems into scalable systems.

I'm Anique — an engineer who builds from 0 → 1. I take rough ideas, broken workflows, and ‘we should probably automate this’ conversations and turn them into products and systems people actually use.

From YC-backed startups to production GTM infrastructure
I. The work

0 → 1, then make it scale.

mess → system → outcome. Select an entry to open it.

0Finding good prospects meant manual research across a dozen tools and stale lists.
1A discovery and enrichment engine that falls through providers cheapest-first until it gets the data, scores what comes back, and runs async so nobody waits on it.
Prospecting runs 24/7 without anyone touching it.
Companies Discovery Scoring Enrichment CRM
24/7
processing
Multi-provider
waterfall
Automated
pipeline creation
II. The method

I like owning the messy part.

The most interesting problems usually don't arrive as clean engineering tickets.

01 Find what's actually broken Talk to the people dealing with it.
02 Make sense of the mess Turn workflows and edge cases into something buildable.
03 Take it 0 → 1 Product, backend, AI, integrations — whatever it needs.
04 Make it survive reality Ship it. Watch it break. Fix what the spec never saw coming.

Product thinking and engineering aren't separate jobs. Treating them like one is most of the trick.

— A working belief —
Good engineering isn't about writing more code. It's about removing complexity from the people using the system.
III. The record

Where I've built

Four companies, one progression — features → products → the systems companies run on.

WithCoverage
2025 → now
Forward Deployed / Growth Engineer
everything so far → one GTM engine

Where it all comes together — product, AI, automation, data, GTM, integrations, internal systems. Most projects start with 'this is currently kind of a mess.' Those are usually the fun ones.

Orbit
Founding Engineer → Engineering Lead
0 → 1 → platform

Joined early. Helped take the product from early-stage to a real platform, then moved into engineering leadership — where the question became what should we build, not just how.

PropReturns YC S21
Founding Team / Lead Technical Engineer
YC startup → production platform

Deep in the 0 → 1 of a YC startup: customer products, internal tools, automation, messaging, infrastructure. No clean boundaries — something needed to work, so we figured it out.

Qode
Full Stack Engineer
it works → it keeps working

Where I learned scale. Automated job discovery, data pipelines, queues, proxies — tens of thousands of records a day taught me the difference between 'it works' and 'it keeps working.'

IV. Right now

Building GTM infrastructure + AI workflows at WithCoverage.

Thinking a lot about what happens when small engineering teams get ridiculously leveraged by AI.

Always down to meet people building interesting things.

V. Correspondence

Got something interesting to talk about?

Founders, engineers, operators, people mid-mess — happy to talk.

Based in India · Working globally

No agenda needed. Say hi.