A multi-database Notion operating system for a UK/US jewelry business
A multi-database operating system replacing six tools, running an entire UK/US jewelry business.
TL;DR
We designed and built the operating system Adamas Studio runs on, an interconnected Notion workspace covering inventory, diamonds, CRM, finance, purchase orders, customer portal, and cross-timezone coordination, with automation layered through Relay.app, custom OCR pipelines, custom automations, and Supabase edge functions. The build replaced what would normally be a stack of expensive enterprise tools with a single workspace tuned to the specific shape of a two-founder, UK/US, made-to-order jewelry business.
The brief
What did the client need?
Adamas Studio was building a jewelry business with two co-founders in different time zones, no operational team, no enterprise software budget, and a product that requires high-touch operational sophistication: bespoke commissions, certified diamonds, multi-stage CAD approvals, vendor coordination across continents, and customer relationships that often span months. The business needed an operating system from day one (the kind of business that doesn't survive its first big order without one).
What they actually needed was infrastructure that could compress the work of a finance team, a project management team, an inventory team, and a CRM team into something two founders could run between them. Off-the-shelf tools individually do parts of this. None of them do all of it, and bolting them together creates more friction than they remove for a business at this stage.
The other constraint that shaped everything was time-zone separation. UK and US founders don't work the same hours. The system had to make that an asset rather than a tax: handovers had to be structured, decisions had to be visible, and neither founder should ever have to ask "what happened while I was asleep?".
The constraints
What made this hard?
Two constraints made this engagement specifically harder than a generic ops build. The first was the diamond layer. Diamonds aren't widgets. They have specifications, certifications, sourcing histories, and customer allocation states that all need to be tracked precisely and pulled from multiple external sources, including the IGI certification API. The build had to handle real-world diamond data ingestion, not abstract inventory.
The second was the customer journey. A bespoke jewelry commission involves an enquiry, a request for quote, CAD design rounds, client approvals, vendor production, quality control, and delivery, with status updates visible to the customer at every stage. This isn't a CRM workflow; it's a project management workflow, a CRM workflow, a production workflow, and a customer portal, all stitched together. Each handoff is a place where information goes missing in less structured businesses.
There was also a budget constraint that shaped every architectural decision. The business couldn't justify enterprise software at this stage. Every component had to either run on tools the founders already paid for, or pull its weight financially within months.
The approach
How did Tincture frame the problem?
A single operating system with multiple surfaces, not a stack of disconnected tools. Notion as the substrate, automation as the connective tissue, and external APIs and edge functions where Notion alone couldn't carry the load. The architectural rule was that data should live in one place and surface wherever it's needed, not be duplicated across systems.
The handover problem got its own dedicated solution. We built an asynchronous handover tracker structured around the actual cognitive shape of a cross-timezone day: decisions made, blockers hit, customer updates, priority shifts. Each founder updates it at the end of their working day so the other picks up exactly where the work left off. The friction goes from "what happened?" to "here's the brief".
We also pushed real automation into the boring layers. Invoice processing in particular: instead of two founders typing invoice data into a spreadsheet, we built an email-triggered Relay.app pipeline with OCR extraction, vendor-and-type categorization, approval routing, and Google Sheets P&L sync. That single workflow recovers hours every week and removes the most error-prone manual step in finance.
The build
What was shipped?
A multi-database Notion architecture covering every operational function. Inventory database for end-to-end jewelry management. Diamond database with IGI API auto-population pulling certification data directly via Supabase edge function and webhooks, tracking stone specifications, vendor source, visual QC status, and customer allocation. Purchase order and invoice system with Relay.app email-triggered automation handling OCR, categorization, approval routing, and P&L sync. CRM tracking enquiry through delivery and aftercare. Customer portal showing live order status, CAD approvals, production milestones, and delivery tracking.
A cross-timezone handover system, "Dear Diary", structured for asynchronous founder coordination. Built around the realities of a UK/US working day rather than pretending the founders are in the same time zone.
An automation layer connecting the databases. Invoice email triggers OCR extraction, categorization, database entry, and P&L sync. Customer enquiry submissions trigger CRM entry and notification routing. Purchase orders trigger vendor communication. Inventory status changes propagate to the dashboards. The friction points where information gets lost in less mature businesses are where this layer is densest.
Operational dashboards across product, operations, finance, and GTM, giving the founders real-time visibility into business health without digging through individual databases. Every number on the dashboard is live, not a screenshot of a number.
The outcome
What were the results?
Adamas Studio runs the business from a single workspace. Every operational function, from initial customer enquiry to final delivery, lives inside the system, with full historical traceability and real-time status. The business operates at a level of operational fluency you'd normally associate with a much larger team, because the system is doing the work a team would otherwise be doing.
The finance layer is the cleanest single win. Invoice processing went from a manual line-item exercise to an email-and-approve flow, with the P&L updating in near-real-time. The founders see margin per project, not margin per quarter. That visibility changes which deals they take and how they price the next one.
What it took
What tools and methods were used?
Notion as substrate, Relay.app for automation orchestration, Supabase for edge functions and IGI API integration and a custom backend layer, Google Sheets as the P&L surface, OCR pipelines for invoice extraction, and a series of custom AI workflows for market intelligence, vendor research, and content support. None of the components are exotic; the work is in how they're stitched.
The methodological move that made this work is treating the operating system as a single design, not a collection of integrations. Most small businesses end up with a stack: a CRM, a billing tool, a spreadsheet for inventory, a Trello board for project management, and a shared Slack channel for everything that doesn't fit, and the information falls through the gaps.
The Tincture Operating Layer is the practice equivalent of what made this work: one workspace doing the work of six tools, designed around the founder's actual workflow rather than the vendor's pricing tier.
The takeaway
What's the transferable principle?
Most early-stage ops failures aren't tooling failures. They're integration failures. Founders pick good individual tools, then spend years living with the gaps between them. The work that compounds is the work of designing the system as a whole: where data lives, how it moves, and what surfaces it shows up on.
The other principle, more specific to founder-led businesses: build for the actual working day, not the textbook one. Adamas Studio works because the system was designed around how the founders actually operate, including the seven-hour gap between when one of them logs off and the other logs on. Generic ops design assumes a single time zone and a team of ten. Most early-stage businesses are neither.
If you're running a business where every operational function lives in a different tool and the founder is the integration layer, you don't need more tools. You need a single workspace designed around how the business actually runs.
Frequently asked questions
More like this
FeaturedAI-native jewelry imagery, from CAD to lifestyle in a single brief
Kora Image Studio
Tincture built Kora Image Studio, a full-stack AI product visualization application that takes a single jewelry design specification and generates CAD line drawings, photorealistic 3D renders, e-commerce product photography, and editorial lifestyle imagery on demand. The studio replaces the traditional pipeline of CAD designer, product photographer, and lifestyle shoot with a single integrated workflow, running on a dual-model Gemini stack with iteration, transformation, and project management built in. Live and in active use, with a single hero specification now seeding entire product catalogues' visual assets.
12 agents, ~10 issues/day, ~2 hours saved daily, cost = Claude subscription + ~$40/month VM
A 12 agent ↔ Linear ↔ Notion setup
The Operating layer was wired to Linear and Notion, paired via MCP, so each specialist agent could ship from Linear and mirror state into Notion against its per-persona write contract, with identity that survives across sessions. Stand-up took about 2.5 working days of focused build, over a week of elapsed time. Steady state: 12 agents working roughly 10 issues or tasks a day, about 2 hours of time saved daily plus the context-rebuilding tax that doesn't show up on a clock. The whole thing runs on a Hetzner VM in Helsinki, so agents pick up Linear comments and project emails whether the laptop is open or not. Cost is the Claude subscription plus about $40 a month for the VM.
FeaturedA weekly Reddit market intelligence engine across trends, competitor SOV, complaints, and pricing
Reddit market intelligence engine
Tincture built a once-weekly automated market intelligence engine for Adamas Studio that scrapes five lab-diamond subreddits (1-1.5k posts, ~20k comments, 30-40k data points per week), extracts structured entities, and delivers actionable intelligence to a Notion dashboard every Monday. The engine covers four dimensions the brand used to make commercial decisions: trend detection (what's emerging or fading), competitor share of voice (who's getting talked about, why, and how), common complaints (where customers are unhappy with the category, surfaced so Adamas can proactively resolve them in product, content, or service), and qualitative pricing intelligence (where the market is settling, what customers consider fair). Built on Python, PRAW, Supabase, ChatGPT API, and GitHub Actions.
Want the operating system your business actually runs on?
We build founder-led operating systems for businesses with operational complexity above their headcount.