Everything we need to get you live
Hey Nico! This is the running answer to your setup doc. It's a live page, so we'll keep updating it as things land rather than firing you a dozen Slack messages. Anything marked with you is yours to run with. Anything marked with Ben is on us, and we'll tick it off here as it's done.
| Product name | Notable |
| Domain | notableaisearch.com (registered) |
| Business model | Option B, managed. Team Empathy creates and configures each client account and bills through our own invoicing. Public sign-up, pricing page and checkout stay switched off at launch. |
| Payments in-app | Not for now. Leave LemonSqueezy in the codebase but disabled. No merchant of record, no tax setup, no Shopify App Store billing conflict. |
| Sign-in | Keep both Google Auth and email magic link. Both are already built, so there's no cost to keeping the pair. |
| User roles | Not needed from day one under the managed model. |
| Task tracking | Jira for Notable. Team Empathy client delivery stays in our own systems. |
| Target | Live within two weeks of us handing over the blocking items below. |
Ben is working through this with a designer right now. You'll get a vector source file rather than raster, so you can generate every size you need from one asset.
Coming to you:
Two things worth saying now. First, hold off on the palette question until the brand lands, since Notable is its own brand rather than a Team Empathy sub-brand, so neither the inherited violet nor our green is the automatic answer. Second, if the new brand fonts turn out to be licensed, we'll confirm web use before you wire them in.
| Domain | notableaisearch.com |
| Registrar | Cloudflare Registrar, bought directly on the Team Empathy account, so no third-party registrar in the loop |
| DNS | Live and active on Cloudflare already. Nameservers benedict.ns.cloudflare.com and lady.ns.cloudflare.com. Nothing to migrate. |
| Your access | Invited as an Administrator on the Cloudflare account, under your own login |
The zone is already active, so you can start adding records as soon as you accept the invite. Nothing is waiting on us here.
SPF, DKIM and DMARC are yours to set up, so the magic-link emails actually reach inboxes rather than spam.
Cloudflare email routing, free, no mailbox to buy. Ben is confirming the public-facing address and the inbox it forwards to. Bug reports and user feedback will land in the same inbox for now, and we'll split them later if the volume justifies it.
Agreed approach on socials: only list profiles that actually exist and have something on them. An empty page linked from the footer reads worse than no link at all, so we'll start with the real ones and add the rest as they fill out.
Company details for the footer, privacy and terms pages are coming from Ben: legal entity name, registered address, company number, the contact address for legal and privacy notices, and the copyright line.
Agreed, and you were right to push for it: a GitHub organisation, not a personal account. It's created and owned by the company rather than by Ben personally, for exactly the reasons you gave.
| Organisation | Team-Empathy-NZ, owned by Team Empathy Limited |
| Repository | Team-Empathy-NZ/notable, private |
| Your access | Admin on that repo, invite sent to nicolas7fernandez-lgtm |
Admin rather than plain push, so you can set the repo secrets for the scheduled jobs yourself without waiting on us. Check your GitHub notifications for the invite.
Still to do as part of setup: the scheduled job currently pointing at the old product's domain needs repointing at ours.
All created under a Team Empathy owner account, with you invited as a named member on each. Ownership sits with the company from day one, you get your own login, and nobody is relaying verification codes across time zones.
These sit on Team Empathy billing with a spend cap on each, so the cost is visible and bounded.
| Anthropic | Done. Key notable-platform, in its own Notable workspace so spend never mixes with Team Empathy's own usage. Billing live. |
| OpenAI | Done. Key notable-platform. |
| DataForSEO | To come |
| Gemini + Perplexity | To come, for the extra engines |
On your point about onboarding cost: agreed, and we want to watch it. Every new client fires a full research and AI visibility pass automatically, so we'll agree a per-client budget before the first real one lands rather than discovering it on an invoice.
Your rules, and we'll hold to them in both directions. Nothing sensitive through Slack or email. Either a one-time secret link, a shared password manager item, or delegated access on the account itself. Delegated access is the preference wherever the service supports it, since no secret changes hands at all.
On Ben, in this order:
On you:
Anything unclear, just ask. A few of these are much easier to talk through than to read, so grab Ben on the weekly if it's quicker.