WHO WE BUILD FOR / JEWELLERS

Websites and automation for jewellers

A custom order is six weeks of "any update?" calls, and last year's wedding customer forgot you exist. We build the catalogue that brings them in — and the workflows that track every order and remember every occasion.

WEBSITE ONLY · AUTOMATION ONLY · OR JOINED — EVERY SPEC SOLD SEPARATELY

What's still done by hand

Every one of these is a workflow waiting to exist. None of them needs new software your team has to learn.

THE REAL COST

Six weeks of custom-order calls, answered from memory at the counter, in front of other customers. And the register of past buyers — the most valuable book in the shop — sits unread while festival season is marketed to strangers instead.

  • Custom orders and repairs are tracked in a register; updates need a call
  • Enquiries about price and availability wait for the owner to reply
  • Anniversaries and past purchases are remembered by nobody
  • New collections are announced to whoever happens to walk in

Two pieces — take one, or join them

Each side is a separate engagement with its own scope and price. Plenty of clients start with one and add the other only when it earns its place.

PIECE A — THE WEBSITE

  • A catalogue site with collections your team updates — no developer
  • Enquiry buttons per piece, capturing size and customization asks
  • Store pages that build trust: certifications, buyback terms, the family story
  • Rate-of-the-day display updated in seconds
WEBSITE SPECS →

PIECE B — THE OPERATIONS

  • Custom order stage tracking — design, casting, setting, polish — sent automatically
  • Repair intake with photos and a promised date, updates on each stage
  • Occasion reminders from purchase history, drafted for your approval
  • New collection announcements to customers who bought in that category
AUTOMATION SPECS →

Three we'd start with

Written the way we'd actually spec them — trigger, steps, outcome. Yours would be drafted from your operation, on the call.

WORKFLOW 01

The order narrator

TRIGGER: CUSTOM ORDER STAGE CHANGES

  1. 01Customer gets the stage update — with a photo where it helps
  2. 02Delays trigger an early heads-up drafted for your approval
  3. 03Ready → pickup message with the final amount and timing

Six weeks of "any update?" calls become six messages.

WORKFLOW 02

The occasion keeper

TRIGGER: ANNIVERSARY OR FESTIVAL APPROACHING

  1. 01Customers with matching history are shortlisted
  2. 02A tasteful reminder with relevant pieces is drafted
  3. 03You approve the batch; replies route to the store's phone

Last year's wedding customer hears from you before the next occasion.

WORKFLOW 03

The repair ticket

TRIGGER: REPAIR ACCEPTED AT THE COUNTER

  1. 01Photos and promised date logged; customer gets the ticket
  2. 02Stage updates send themselves; delays notify early
  3. 03Ready → pickup reminder until collected

The repair register stops ringing your counter phone.

The questions your customers repeat

A chatbot grounded in your own pages answers these in seconds, cites the source, and hands anything unusual to your team.

  • What's today's gold rate? Making charges?
  • Is my order / repair ready?
  • Do you buy back or exchange old gold?
  • Can you make this design in my budget?
  • Are the diamonds certified? Hallmarked?
HOW THE CHATBOT SPEC WORKS →

What stays human

Automation earns its keep on the repetitive work. These lines don't move — they're where your judgment and your relationships live.

01

The craft and the counter — trust is built face to face over a velvet tray

02

Valuations and buyback — a person weighs, tests, and quotes

03

Every outbound message — occasion reminders send only after you approve the batch

Asked by jewellers

Jewellery customers expect personal treatment. Won't automation feel cold?

Every customer-facing message is drafted in your voice and approved by your people. The automation does the remembering; the relationship stays yours.

We can't show prices online — they change daily.

The rate-of-the-day updates in seconds, and per-piece enquiries can route to the counter instead of showing numbers. Your call, piece by piece.

Is purchase history safe to use like this?

It stays in your systems; workflows read the minimum needed to draft a reminder, and nothing sends without approval. Documented end to end.

Our customers span three generations. Will older customers cope?

They receive ordinary WhatsApp messages and reply normally — nothing to install, nothing to learn. The system is invisible to them.

Design photos are sensitive before delivery. Who sees what?

Stage photos go only to that order's customer, and you choose which stages include images at all.

Do we have to take both the website and the automation?

No. Every service is scoped and sold separately — website only, automation only, or a single workflow to start. The two compound when joined, which is why the page shows both, but nothing requires buying both.

Tell us what your team still does by hand.

Thirty minutes. You'll leave knowing what we'd build, what it would cost, and whether it's worth doing at all.

Prefer to write first? Use the full form.