Fast Web Labs

What we test in hours
before selling it in weeks.

No client projects in here. Experiments: things we build fast to find out whether an idea holds up, how long it takes to stand up, and what makes somebody share it. Some are still running, some are archived, and some never reached production.

The ones that went badly are published too, and any figure that does not come from a client in production says it was measured in testing. A lab that only shows wins is a portfolio with another name.

LAB / 001Running
Fecha
August 2026
Build time
4 hours

Farmear Aura

An aura test, a voted ranking and one-on-one battles, built while the trend was still hot.

What we were testing

If a mechanic is simple enough and lands in time, is somebody else’s trend enough to carry it?

What happened

Zero to production in an afternoon: domain, database, voting, battles with their own URL and a finished look. No viral traction.

What we learned

The speed is real and demonstrable. Somebody else’s trend is not distribution: with nobody to show it on day one, a good mechanic never starts.

StackNext.jsSupabaseVercel
Open it
LAB / 002Prototype
Fecha
2024 – 2025
Build time
Weeks

Catalogue agent over WhatsApp

An agent answering catalogue questions over WhatsApp by searching the real products, not what the model imagines.

What we were testing

Can a catalogue business handle its enquiries without the agent inventing products or prices?

What happened

In testing it resolved 85% of enquiries with sub-3-second answers, escalating to a human when unsure. Never reached production.

What we learned

Retrieval over the real catalogue is what separates a useful assistant from one that makes things up. The bottleneck was not technical: the project lost its owner.

Stackn8nGeminiQdrantRedisBaserowWhatsApp
LAB / 003Prototype
Fecha
2024 – 2025
Build time
4 weeks

Field work reports

An app for a technician to close the report on site: photos, customer signature and a PDF filed before leaving.

What we were testing

Can paper be removed from a field operation without asking the technician to learn anything new?

What happened

Working end to end: ID login, location lookup, signature and media capture, and a PDF generated and archived on its own. Never reached production.

What we learned

Adoption is not decided by the app: it is decided by how many taps it takes one-handed, wearing gloves.

StackReactGoogle Apps ScriptDrive APITailwind
LAB / 004Prototype
Fecha
2024 – 2025
Build time
Weeks

Document intelligence

Documents dropped into a folder come out as database rows, with the database itself as the only interface.

What we were testing

Can a small business stop retyping data from documents without buying an ERP or changing how it works?

What happened

In testing, extraction under 5 minutes per batch and 98% accuracy on the defined fields. Never reached production.

What we learned

The value is not in extracting: it is in going back and pulling a new field out of everything already processed without redoing the work.

Stackn8nBaserowOCROpenAI

Got an idea nobody has built yet?

What we do in the lab is exactly what we do for a client, minus the invoice: understand the problem, stand it up fast, and look at the numbers without dressing them up.

Message us on WhatsApp