e11

Proof

Real work, told in the tone it was done in.

A rebuild reads like a ledger. An audit reads like a broadsheet. A student's site reads like a log. A WhatsApp build reads like the four messages it took. No single template, because no single kind of work.

Every card links the artifact itself where consent allows, and says plainly where it stops. Client names appear only with a yes.

Founder

I'm Abhishek. I worked in AI for years and left the job to build things for Indian small businesses myself. AI writes the code now; my job is to make sure what gets built actually works and stays working.

Everything we make runs on datacenters, so the company is wherever the founder and the front door are: the villages of Gonda, the mountains of Jibhi, the next place the road goes. What stays put: two registered companies, real invoices, one phone that answers.

Four lanes, four registers

Each case study in the shape of its own work.

Rebuild ledger
Live

Phoenix · punah

yaqutali.com: a journalist's WordPress site, rebuilt static and handed back owned.

The site kept its design and its words. What left: the PHP runtime, the plugin surface, the admin login that botnets scan every minute. What arrived: a directory of HTML, CSS and images that any host can serve, and a monthly site-care rung so it stays that way.

Before
WordPress, shared hosting, plugin-dependent
After
Static, 13 KB homepage document, no server-side code
Ownership
Customer holds the domain, the repo and the bundle
Care
Site Care, ₹1,111 a month, in or out any time
Wiring ledger
Live

Ailyak · our own stack

Sarai: a hotel's OTA feed, wired into one lead ledger, run on a property we own.

Ailyak runs two mountain stays in Jibhi. Booking.com and Hostelworld have no usable booking APIs, so every reservation arrived as an email and every enquiry as a WhatsApp message, reconciled by hand against a spreadsheet. Nothing was rebuilt: the property management system stayed. What was wired: the OTA emails are parsed into a phone-keyed session ledger, direct WhatsApp enquiries land in the same ledger, and an operator console pushes confirmed stays into inventory, takes the deposit, and warns when a lead is going cold. Ailyak is our own company. This is the stack we run, not a testimonial.

What was ageing
OTA emails, a shared spreadsheet, bookings keyed by memory
Wired, not rebuilt
Email parsing, OTA-room to PMS-room mapping, signed webhooks into the existing PMS
Operator console
Installable PWA, push alerts for leads going cold, assistant drafts the WhatsApp reply on a key we hold
Receipts
Refinement waves 1 to 4 shipped 15 Aug 2026; inbound funnel live; console in daily use at both properties

Console and repository sit behind an access gate for the property team, so there is no public URL to open. The founder's own daily use is the proof; a walkthrough is available on request.

Findings broadsheet
Live

Dhara · audit engine

An external-surface read, delivered as a report you can hand to a board.

Dhara reads what the internet can already see about a company: reachable services, software versions, exposed admin paths, the one CVE that is version-confirmed and actually exploitable. The sample report is a real render of the real template, on a sanitised target, so you can judge the artifact before you judge the engine.

Artifact
Report v2, paper-first broadsheet, Launch Design
Claims
Only version-confirmed CVEs are named; guesses stay unnamed
Your control
Opt-out column on the masthead, nothing scanned twice without consent
Lane
DPDP-readiness for Indian SMBs; wedge audits for the mid-market
Learner's log
Live

Architect · a matter of one's own

Semicolon: a student's first production site, built with a mentor and a tool, running on a real box.

Anshuman started Semicolon on an old laptop, learning while building. A matter on Architect remembers the journey and carries one line from the mentor into every session: be supportive, let them wander. Eleven pages, CI that ships a public image, and Ada, the site's own assistant, answering through a live model on a key Anshuman controls.

  1. 01

    Starting it on the old laptop. At the beginning I did not really know how everything worked. I was learning while building, breaking things, fixing them, slowly understanding how the pieces connected. It started as an idea, and I wanted it to be a real coding website people could actually use.

  2. 02

    The bugs and the deployment problems. Things worked locally and failed online. I spent a lot of time on Docker, the server, CI and the API. Some errors were frustrating, but fixing each one taught me something. Even keeping the laptop running late at night became part of it.

  3. 03

    Seeing Semicolon running publicly. The code was no longer just sitting on my laptop. CI was building the image, it was deploying to a real server, and Ada was responding through a live model. That made the whole project feel real.

Built by
Anshuman. The tools helped; the learning, the decisions and the testing were his.
Shipped via
GitHub Actions → public image → zero-credential pull on a fleet box, every 2 minutes
Mentor's role
Hosting, trust boundaries, one annotation that travels forward
Assistant
Ada, live on an OpenRouter key the builder owns, with a monthly cap he set

Told in the builder's words, shaped with his yes, reviewed by him before it went up.

Four WhatsApp beats
Staged, go-live pending

Phoenix · brochure, re-homed

A Gonda, Uttar Pradesh food brand's 2019 brochure site, rebuilt over four WhatsApp messages.

No portal, no brief document, no call scheduled. The owner sent a logo and seven product packs on WhatsApp; a static preview came back staged on their own domain. One new thing was added: an order button that opens WhatsApp, replacing a 2019 online-order page that never ran. The story is written as the four beats it took.

Intake
WhatsApp thread, logo plus seven pack photos
Preview
Staged on the customer's domain, noindex, behind a holding page
New
Order on WhatsApp, a working wa.me deep-link
Care
Site Care rung from day one

Named and linked after go-live, with the owner's yes.

Sayable links

Short enough to say on a call.

Every artifact on this page has a path you can read out loud. They don't change when the file behind them does.

Getting started is simple.

Make a wish. Watch it come true with 11.11.

Say what you want built, in one line, on WhatsApp. A person reads it, a person replies, and if it is a homepage rebuild the first one is free so you can see it on your own site before deciding anything. Ready for the leap?

Direct line

Consultation requests stay owned. We reply from e11 after reviewing fit and timing.