Unova

a small scout that finds what people are searching for

Warming the filament

The engagement

Four phases. You always know which one you’re in.

  1. 01 Week 1

    Interrogate

    We pull the problem apart before anyone opens a design tool. What the data actually looks like, who touches it, what breaks today, and which of your requirements is really a solution in disguise. You get a written read of the problem — including the parts we think you shouldn’t build.

  2. 02 Weeks 2–3

    Architect

    Data model, boundaries, and the one or two decisions that are expensive to reverse. We argue these out properly and write down what we chose and what we gave up, so in eight months nobody has to reverse-engineer the reasoning from the code.

  3. 03 Weeks 3–10

    Build in the open

    Working software on a real URL from the first week, updated continuously. No milestone reveals, no big-bang demo. You watch it become the thing, and you get to change your mind while changing your mind is still cheap.

  4. 04 Ongoing

    Prove and hand over

    Vitals, contrast, crawl coverage and load numbers measured on real devices, before and after. Then documentation, a walkthrough, and access to everything. You should be able to fire us without it being an event.

How we work

Cinematic on the surface. Boring, in the best way, underneath.

  • Content first, spectacle second

    Every page here is real HTML. The 3D layer is enhancement — turn it off and nothing breaks, nothing disappears, nothing stops ranking. We build the same way for you.

  • Measured, not asserted

    Core Web Vitals from real devices, not lab runs. Contrast checked against the worst frame, not the best one. If we claim a number improved, you get the before and the after.

  • The data model is the product

    Interfaces are cheap to change and schemas are not. We spend the first week on the thing everything downstream inherits, which is why the third month goes quickly.

Rebuilds nobody asked us for.

All rebuilds

Not client work. These are independent concept rebuilds of real local businesses, done on our own initiative. The owners have not seen them and have not endorsed them.

  • Hospitality

    KIOR — The Door Cafe

    An all-day vegetarian café built around a hand-carved Rajasthani door. We rebuilt it as a video-led single scroll: menu, gallery, story and a WhatsApp line, with the whole thing readable before any script runs.

    5 sections Video hero, menu, gallery, story

  • Hospitality

    Koala Caff

    A coffee house with a slow-down premise. The rebuild uses numbered section navigation so the whole page reads as one deliberate sequence rather than a stack of blocks, with a photographic gallery and a table-booking flow.

    5 sections Numbered nav, gallery, bookings

  • Hospitality

    Anokhi Café

    An organic, farm-to-table café inside a block-print store. The rebuild treats the menu as real HTML text rather than a photographed PDF — which is what makes it readable by a screen reader, quotable by an answer engine, and fast on a phone.

    Text menu Machine-readable, not a photo

Tell us what you’re building. We’ll tell you what it actually takes.

No discovery-call theatre. Send the problem and you’ll get a real technical response — scope, risks, and the parts we think you shouldn’t build.

Start a project