If you are serious about digital infrastructure,
this is how Solanki Jewellers should run.

Not a pitch. The architecture.
Built for one shopMalurSep 2026

01 — where it stands

The shop already owns everything it needs.

None of it is switched on.

What the shop has
What it does with it
2,730customers, named and numbered
Sits in a spreadsheet. Reaches nobody.
35 yearsof trust in one town
Ends at the door. Nothing carries it further.
The stockstanding in the counter
Seen only by whoever walks in today.
Every salealready recorded, every day
Stops at the till. Nothing reads it back.

Four assets. Four dead ends.
Nothing here needs to be bought. It needs to be wired.

02 — the shape

Three surfaces. One spine.

Not three projects. One system wearing three faces.

COCKPIT
private · the operator
where the work happens
CATALOGUE
public · the stock
one page per piece
SITE
public · the shop
not built yet
ONE DATABASE
customers · stock · photographs · every action, dated
one login · one operator · one source of truth

Change a fact once. Every surface tells the same story.

03 — what already exists

Two of the three are done.

Not designed. Not demoed. Running.

Cockpit
The operator's tool
● Live · in daily use
Contacts · Review · Segments · Runners · Queue · Customers · Pieces · Performance
Catalogue
The stock, public
● Built · not yet shown
Entered and photographed from a phone at the counter. Publishes itself.
Site
The front door
○ Not built
Ships with the catalogue. Neither goes alone.
The data wire
Sales into the system
▲ Not open
The one piece not in this side's hands. Section 04.
2,730
contacts
live
32
message
patterns
6
collections
27
schema
versions
38
decisions,
written down
₹0
running
cost

04 — the missing wire

The billing software already knows everything.

Who bought. What. When. It has never once been asked.

Today

BILLING SOFTWARE
GST · local database · at the counter
who bought · what piece · when
how much · how often
— captured already, every single day
THE SYSTEM
knows the names, and nothing about what any of them ever bought
— so every message is a guess,
and a guess has to be picked by hand

Not connected

Open the wire

THE SAME RECORDS
read out on a schedule
nothing re-typed, nothing changed
the shop bills exactly as it does today
THE SYSTEM RECOGNISES
the buyer, the piece, the date
the pattern, the right moment
— and stops guessing

This is the single most important move on this page.
Everything below is impossible without it, and straightforward with it.

05 — how it runs

Controlled automation.

Not a blast. A shop with this reputation does not need a thousand hits at once — it needs the right one, at the right moment, every time.

NOW

Manual

built · running today
The system
holds the book
writes the message
The human
picks who
reads it
taps send
01

Patterns fire themselves

needs the wire
The system
sees the sale
knows the occasion
writes, queues, waits
The human
confirms
sends
02

The queue drains itself

once 01 has proven itself
The system
paces the sending
holds back the wrong ones
reports what went
The human
supervises
overrides
03

The cockpit runs itself

the destination
The system
runs the calendar
runs the follow-ups
flags what needs a person
The human
sets the policy
reads the numbers
Bulk sendingPaced. Human-shaped.
Everyone at onceThe right list only.
LouderBetter timed.
More messagesFewer, that land.

The number on the shop board is the customer relationship.
Quality control is not caution here. It is the whole design.

06 — the loop

Then it starts feeding itself.

Every sale makes the next message better. That is the whole machine.

A SALE
happens at the counter
BILLED
recorded, as it already is
RECOGNISED
the system knows who and what
THE RIGHT MOMENT
not the loudest one
THEY COME BACK
to a shop that remembered
THEY SHARE A LINK
one piece, sent to one person
A NEW CUSTOMER ARRIVES ALREADY KNOWING
— and the loop runs again, one turn wider than before

Word of mouth is the shop's oldest asset. This gives it something to travel on.

07 — getting known

A brochure is three pages. A catalogue is a hundred.

Every piece is its own page, its own link, its own way in.

A normal jeweller's website

Three pages. Nothing to search for, nothing worth sending to anybody.

This one

One page for every piece standing in the counter. Each one findable, each one sendable, and each one opens carrying that piece's own photograph and its own name.

The stock does the marketing. Nobody has to write a campaign.

08 — the order

This is not a calendar. It is a chain.

Each link opens the next one. Skip a link and everything after it cannot be built.

Track A — the shopfront

PHOTOGRAPHS
the real stock, shot to a standard
SITE + CATALOGUE
on the shop's own address
FOUND, AND SHARED
by customers, to customers

Track B — the system

THE DATA WIRE
billing → relay
PATTERNS
post-purchase, occasion, repeat
THE QUEUE DRAINS
paced, supervised
IT RUNS ITSELF
a person sets the policy

Track A is waiting on photographs.
Track B is waiting on one decision.
There are no dates on this page on purpose — dates follow decisions, they do not replace them.

09 — boundaries

What this is not.

Said plainly, so nobody has to guess about it later.

A websiteA system that happens to have pages.
A campaignInfrastructure. It runs after anyone stops watching.
Bulk WhatsAppOfficial, safe, and the shop's number stays clean.
A templateBuilt for this shop. Nobody else runs it.
An app to installA link. It opens on whatever is in your hand.
A prototypeLive, on real data, every change versioned.

10 — how the work moves

One operator. One project. No parallel lanes.

Not a team, not an agency, and not somebody who will be here in the gaps between two other jobs.

35
days on
this build
234
commits
1
repository
1
shop
38
decisions,
each with its reason
0
other shops
running this

Every decision in this system is written down the moment it is made — what was chosen, what was rejected, and why. A year from now nobody has to remember.
That is the difference between a system and a favour.

The shop has been run seriously for thirty-five years.
This is that same seriousness, pointed at the other half.

MOVE 01

See it.

Meet, and open the catalogue on your own phone. Ten minutes. It is built, it is running, and it has never been shown to you.

MOVE 02

Open the data.

The billing software's records reach the relay. Nothing changes at the counter, nothing gets re-typed, and the shop bills exactly the way it does today. Everything on this page that is not yet built starts here.

Everything above this line is built, or drawn and ready to build.
The only thing missing is a decision — and a decision is the one thing that cannot be built for you.