Drawing register

Proof, framed by what it demonstrates

A club platform is multi-tenant SaaS engineering. A drawing set becoming a priced bill is document intelligence. Read these for the engineering underneath rather than the industry on top, because the industry on top is the part least likely to be yours.

Five pieces of work: three live, one a prototype and one a proof of concept. Nothing here is described as more finished than it is. What each word means.

Sheet: A-01
Title: Work
Issued for: Information
Drawn by: Snilld

W-05Nexus

Offline-first multi-tenant business appSales and business developmentLive

A morning briefing: pipeline value, deals won this month, conversion rate, today’s priority deals and what is due next. — Preview · W-053 screens

An analytics screen with a conversion funnel, a revenue heatmap, days spent in each stage and a won-to-lost ring. — Preview · W-053 screens

Sheet W-05 · Offline-first multi-tenant business app · Sales and business development

Live

Our sales cockpit: a morning briefing, the pipeline as a board, contacts and companies, a timeline of every call and message, and a page per customer once the deal is won. Multi-tenant, invite-only, and usable without a signal.

A customer page for an invented company, with lifetime revenue, order history and tabs for notes and activity. — 03 / 03After the deal is won

Demo data. Every name and number is invented.

Goes in: Deals in a spreadsheet, notes in WhatsApp, follow-ups in someone’s head
What we built: A local-first app that reads from a validated copy in the browser and syncs a queue of changes
Comes out: A briefing, a pipeline and a timeline per customer, on any phone, with or without signal
The line it does not cross: The server takes the workspace from the signed-in session, never from the request, so one company cannot read another’s

Note 1 · The constraint

A small sales team works from its CRM all day, often on a phone with a weak signal. Most CRMs answer with slow page loads and a grey table per screen, so the real notes end up in WhatsApp and the CRM falls behind the truth.

Note 2 · What transfers

Any team that works from a phone away from a desk, in sales, service, collections or site visits, needs the same two things: a screen that is fast on a bad connection, and data that is never shared across customers. The same design carries to a field-service log, a dealer portal or a case tracker.

Business app: Multi-tenant, invite-only
Sign-in: Google
Automated tests: 199 app, 27 API
Hosting: Cloudflare Pages and D1
Runtime dependencies: None
Public demo: Invented companies, no sign-in

The full write-up →crm.snilld.in →

Legend

How to read this register

Four status words and two rules. The words are load-bearing: each one is a claim about how finished something is, and we use them literally.

Live: Running in production and used by people who are not us. If it says live, you can look at it.
In build: Being built now, with a client, against a date. Some of what is described is working and some of it is not finished.
Prototype: Demonstrates a design rather than carrying real load. Where the stored state is simulated instead of a production database, the facts panel says so.
Proof of concept: Proves the hard part works on real inputs. It is not a product and it is not in production.
Clients: Anonymised. No client is named unless they have given written permission, so most entries describe the organisation rather than naming it. The constraint and the engineering are described exactly as they are.
Numbers: No accuracy or confidence figure appears anywhere on this page, because none has been measured under conditions we would be willing to publish.

W-05Nexus

Note 1 · The constraint

Note 2 · What transfers

How to read this register

Two of these are platforms we operate