Qelv

Labs

We build the prototype before we ask you to believe the proposal.

Working software, not slides, built to settle an argument about scope in one sitting. None of them was built for a paying client; each settled a scope question before a build started. For delivered work, see the work page.

Prototypes
7

each with its own page on this domain

Captures
6

across 2 of them, stepped through on the page

Demos you can run
2

in your browser, on sample data, sending nothing

Delivered to a client
None

built to settle scope; nothing here counts as work

7 prototypes

Each one built to answer a scoping question.

In the order they were built. Every card says what a reader can open now, and what a booked walkthrough adds.

Discovery demo

Order management system

Orders, price lists, purchasing, inventory, shipping, payment, and an audit trail: the operations spine of a distribution business in one surface. Built twice; the second pass, with a partner team, came at it from the buying side, with supplier baskets, allocations and per-line margin. Reviewed by the prospect's own team against a line-by-line requirement tracker and revised through two gap-closure waves.

What it shows you

Two answers to one brief and what the second got right, how a prospect's team reviews a prototype against a requirement tracker, and how a custom operations system replaces six spreadsheets without becoming an ERP project

Open now
Driven on a call
Read why there is no linkBook a walkthrough

Prototype

Automated order intake

Reads incoming order emails and turns them into stock movements, quotations, orders, and an audit trail, with nobody retyping an attachment.

The prototype dashboard: four counter cards across the top and a recent-orders list below, each order row carrying a state and two actions
Prototype, sample data. The dashboard, with the demo database behind it.

What it shows you

What email-to-system automation looks like when it is working

Open now
5 captures, and a demo that runs in your browser
Open the prototype pageBook a walkthrough

Prototype

Morning ads-ops agent

Takes the ad-platform exports an ops person opens every morning and assembles the report they would otherwise have built by hand.

The ads-ops prototype's start screen: a drop zone for a CSV or JSON export, a start and end date, a demo mode button, and an empty report panel
Prototype, sample data. An export goes in here, or the demo data does.

What it shows you

A recurring manual report removed, in a pattern your team can reuse

Open now
1 capture, and a demo that runs in your browser
Open the prototype pageBook a walkthrough

Prototype

Content operations dashboard

A working surface for SEO and content teams: briefs, pipeline state, and publishing status in one place instead of a shared sheet.

The content operations prototype: a dashboard of content briefs with their pipeline state and publishing status
Prototype, sample data. Briefs and pipeline state in one surface

What it shows you

How we prototype a team's workflow before committing to build it

Open now
Driven on a call
Read why there is no linkBook a walkthrough

Discovery demo

Financial data to article drafts

A workflow-platform automation that pulls financial data from company websites and drafts articles from it. Built and shown live to a trade-intelligence publisher that wanted a real editorial job automated, not a technology demo.

What it shows you

What an extraction-to-content pipeline looks like on a workflow platform, and where a person still has to sit in it

Open now
Driven on a call
Read why there is no linkBook a walkthrough

Elsewhere on the site

Related

Where to next

Want one of these built around your own workflow?

A working version in two weeks. Not a specification document, not a deck: something your team can click and argue with.

Send us the bottleneckAbout the Two-Week PrototypeWhere the numbers come from

We reply within two business days. If it is a fit, you get a one-page note on what to do first, before any sales call.