A product schema that can't hold a protocol
Compound, purity, quantity, lot, COA, storage — defined fields, not a free-text box. There is nowhere to paste a dosing protocol, which is why nobody ever does.
Website design
A storefront where compliance is structural.
Most research-use sites are a normal store with a disclaimer bolted to the footer. Ours is built the other way round — the controls are in the structure, so the site stays compliant whether or not anyone remembers the rules at 11pm.
What every build includes
One scope, one price. No tier where the cheap version is the worse version.
Everything a store needs.
Researcher gate at the door
Age and counterparty affirmation before the catalog renders, with the intended-use attestation captured at checkout. Direct product URLs are gated too — no side entrance.
COA handling with lot linking
Certificates attached to the lot they belong to, surfaced on the product page, and resolvable from a QR code on the vial. Broken and stale links get flagged automatically.
Up to 100 products loaded
Imported from your CSV, cleaned, categorised and mapped to the schema. Architecture that still makes sense when the catalog is four times the size.
Checkout and transactional email
Working cart, checkout, order confirmations, shipping notifications and receipts. The full page set — shop, product, cart, about, contact and every policy page.
Product schema markup and SEO
Structured data so search engines and AI assistants describe your catalog accurately. Titles, meta, sitemap and clean URLs done at build time, not sold back to you later.
How two weeks runs
The clock starts when your brand assets and catalog arrive — not when you sign.
Fourteen days, then live.
Days 1–2Kickoff
Assets in, decisions made
You send the logo, brand colors, product CSV, COA files and any policy copy you already have. We settle the design direction from a defined set — type, palette, product card layout — so nothing stalls on taste later. If a site already exists, we scan it first and tell you what carries over.
Days 3–7Build
The store gets assembled
Template configured to your brand, catalog imported and mapped to the schema, every page built, COAs attached to their lots. By the end of the week there is a real storefront on a staging URL you can click through.
Days 8–11Compliance & review
Gate on, scan run, one revision round
Researcher gate and attestation flow installed, then the full scan against your finished content. Anything it finds gets fixed before launch. This is also your revision window — one consolidated round, which is why we ask for it in writing rather than in pieces.
Days 12–14Launch
DNS, SSL, live, monitored
Hosting provisioned, certificates issued, domain pointed, transactional email verified and tested. The site goes live and monitoring starts the same hour — you are never live and unwatched.
Your side of it
Builds run late for one reason: waiting on content. This is the whole list.
What we need from you.
Logo files
Vector if you have it. If you don't, we'll work from what exists or quote a redraw.
Product catalog as CSV
Name, description, quantity, price, lot number. Messy is fine — we clean it.
COA files
PDFs with the lot they belong to. A folder and a naming convention is enough.
Domain access
Registrar login or the ability to change DNS records when we ask.
One person who can decide
Available for a kickoff call and one round of consolidated feedback. That's the real ask.
If you need more
Priced on the page so a "can you also…" never turns into a negotiation.
Add what you actually need.
Additional productsPer block of 100 SKUs beyond the first hundred
$250
Custom homepageDesigned from scratch rather than configured from the system
$750
Marketing email automationKlaviyo setup, abandoned cart, welcome and win-back flows, copy written
$850
SMS notificationsTwilio integration for order and shipping alerts
$500
Blog setup and first postsStructure, categories and three written articles
$600
Product copywritingCompliant descriptions written for you, per product page
$40
Anything elseScoped and quoted before a minute is billed
$150/hr
What it costs
Published, because nobody else in this category will tell you without a call.
Two numbers, one reason.
Build + processing
from$1,800
Plus $195/mo and 7% + $0.10 per transaction — with the monthly fee waived above $50k in volume.
Build only
$3,000
Same build, same quality, no processing relationship. Monitoring available separately at $295/mo.
The difference isn't the work — it's identical. We can discount the build for processing clients because we earn on volume over time, and we'd rather have you live than have your deposit. Builds carry a 12-month processing commitment; leave earlier and the balance of the standard build price becomes due. "From" pricing reflects that a storefront needing heavy remediation before we can start is quoted after we've seen it.
Questions
The four that come up before anyone signs.
Asked and answered.
Is this a template or a custom design?
It's a system we built, configured for your brand. Your logo, your palette, your type, your photography, your product card treatment — real design decisions, made inside a structure that has the compliance controls designed into it.
What it isn't is a blank canvas, and that's the point. The constraints are the product. A site where anyone can drop a free-text block onto a product page is a site that will eventually have a dosing protocol on it.
If you want a homepage designed entirely from scratch, that's the $750 add-on and we're glad to do it — on top of a structure that still holds.
What actually makes two weeks slip?
Content, almost always. The build itself is predictable; waiting on a product CSV or a logo file isn't.
The clock starts when your assets arrive, not when you sign — so a slow week on your end doesn't quietly become our delay. If something is genuinely blocking us, you'll hear about it the day it happens rather than on day fourteen.
The other one is scattered feedback. One consolidated revision round is in scope. Five separate rounds of "one more thing" is how a two-week build becomes a six-week build, which is why we ask for it in writing.
Do I own the site?
Yes. Your domain, your content, your database, your Stripe account. Nothing is held hostage.
If you leave, the site exports in a working state and goes with you — a standard WordPress and WooCommerce install that any competent developer can pick up. The gate and monitoring are ours and switch off, but the storefront is yours.
We put this in writing because in this vertical people have been burned, and a clean exit path is worth more than a promise.
What if my catalog is much bigger than 100 products?
Additional products come in blocks of 100 at $250. The catalog imports from CSV, so what you're paying for is cleanup and mapping rather than typing.
Large catalogs also change the architecture — categories, filtering, search and URL structure all need to be planned rather than grown into. That work is included; we'd rather build it right on day one than migrate you off a structure that broke at 300 SKUs.
Currently booking Q4
Two weeks from now, you could be live.
Send your URL, or tell us there isn't one yet. Either way we come back with a written read on what a build would involve — before anyone talks about deposits.