Team Empathy × Nico · Build Kickoff

Everything's ready

Your setup doc, answered end to end

Updated 6 August 2026 • Living document, we'll keep adding to it

Hey Nico! This is the running answer to your setup doc, and the short version is that everything on our side is done. Domain, DNS, GitHub, every account, all the API keys, and the full brand pack.

You should have invites waiting for GitHub, Cloudflare and DataForSEO, and your two API keys came through Slack as one-time links. The brand zip is attached in the channel.

It's a live page, so we'll keep it updated as things move rather than firing you a dozen Slack messages. Anything marked with you is yours to run with.

You're unblocked. Nothing on this page is waiting on us any more. The two-week clock starts whenever you're ready, and the first milestone is the source landing in the repo.

Done With you With Ben Blocking

The decisions, settled

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.

On self-service. Managed first doesn't close the door. The self-serve machinery stays in the codebase and we may switch it on later. If someone wants the platform before then, we'll onboard them and invoice directly.

1. Branding Done

The full brand pack is attached in Slack as a zip. Notable has its own identity rather than a Team Empathy reskin, so the palette is genuinely its own.

The direction is called Tide: light canvas, deep teal blocks, teal accent.

Block colour	`#0B3B4A` — hero, CTA and footer bands, app sidebar
Accent	`#0E7490` — CTAs, links, key data
Light accent	`#7FD8EC` — blocks only, see the warning below
Default theme	Light. Dark is app-only; marketing is always light.
Fonts	Manrope 700/800 display · Hanken Grotesk 400/500/600 body · JetBrains Mono 400/500 labels. All Google Fonts under the OFL, so self-host those weights.
Icons	Lucide, 24×24, 2px rounded stroke. ISC licensed.

What's in the zip:

12 logo SVGs in assets/logo/: horizontal, stacked and mark-only, each in colour, white, black and reverse. The wordmark is outlined, so every file is self-contained and renders identically in an <img> tag, in Figma, or on a machine without Manrope installed.
Full favicon set in assets/favicon/: favicon.svg, a dark-scheme variant, PNGs at 16/32/48/180/512, and apple-touch-icon.png
Open Graph image, 1200×630, in assets/og/
All tokens as CSS custom properties in assets/tokens/notable-tokens.css, structured to drop straight in, including chart colours and a [data-nt-theme="block"] scope
Notable Brand Guide.dc.html — the spec: logo rules, clear space, minimum sizes, measured contrast ratios, block usage
README-notable-brand.md — start here, it maps every file to its use

The one rule that catches people. The light accent #7FD8EC is block-only. It reads 7.4:1 on the block but only 1.6:1 on white, so it must never carry text, icons or borders on a light surface.

Every colour token ships with its measured contrast ratio in the comments, so you can pick confidently without re-checking accessibility as you go.

2. Domain and DNS Done Records with you

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.

3. Email With Ben

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.

4. Socials and company details With Ben

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.

5. GitHub Done Accept your invite

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.

First milestone. The first payment is triggered by the complete source landing in that repo. It's ready and waiting for you, so this is the one thing that unblocks everything else.

First milestone. The first payment is triggered by the complete source landing in that private repo. So getting the org up is the very first thing on Ben's list, and the code being in version control is the thing that unblocks everything else.

6. Accounts All created Accept your invites

All created under the Team Empathy owner account, with you invited as a named member on each. Ownership sits with the company, you get your own login, and nobody is relaying verification codes across time zones.

Vercel	Created. Upgrading to Pro, since the scheduled jobs and long content runs need it.
Neon	Created
Resend	Created. The `notableaisearch.com` domain and its SPF, DKIM and DMARC records are yours to add.
Upstash	Created
Cloudflare	Invited as Administrator
GitHub	Invited as admin on the repo, per section 5
DataForSEO	Account funded, you're added as a collaborator

On account structure. Everything sits under our teamempathyaccess account so ownership and billing stay in one place, with named access for you on each service rather than shared passwords. Sing out if that causes you any grief in practice and we'll rethink it.

7. Paid API accounts Anthropic + OpenAI done Rest with Ben

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	Done. Account funded and you're added as a collaborator, so no shared password. Note the login and password are the API credential.
Gemini + Perplexity	To come, for the extra engines. Tell us if you want them from day one.

Your keys are on their way. Both keys have been sent to you directly in Slack as one-time secret links, deliberately not posted on this page. They self-destruct the moment they're opened, so open each once, save it straight into your environment, and give Ben a shout if either link is already dead so he can reissue it.

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.

One thing to note. Team Empathy already runs Anthropic and OpenAI keys for its own internal systems. Notable gets brand new keys with their own caps, never the existing ones. That keeps platform spend separate from ours, so we can see the true cost per client and price properly, and a runaway job on one side can never take down the other.

8. Sending credentials With you

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.

What happens next

Done on our side:

~~Domain registered~~ — notableaisearch.com, DNS live on Cloudflare
~~GitHub org, private repo, your invite~~
~~Anthropic and OpenAI keys~~ — sent via Slack
~~DataForSEO~~ — funded, you're a collaborator
~~Cloudflare, Vercel, Neon, Resend, Upstash~~ — all created
~~Brand pack~~ — attached in Slack, outlined logos and all tokens

Still coming from us, none of it blocking:

Company legal details for the footer and legal pages
The public email address and the inbox it forwards to
Social profile links, once there are real ones to point at

On you:

Accept the invites: GitHub, Cloudflare, DataForSEO
Get the code into the repo. That's the first milestone and it unblocks everything else
Flag anything on this page that's wrong, missing, or that we've misread from your doc
Tell us the moment something is holding you up, rather than working around it

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.