01every 15 min
Time-based trigger
Apps Script on your account checks every 15 minutes which contacts changed on either side since the last run.
Add a contact on your phone — it lands in your Clients directory in Notion, with full field mapping, not just a name and a number. Nothing to remember to re-enter — deployed on your own Google account, two-way, no manual work.
A new contact lands on your phone the moment you first talk to someone. It lands in your CRM in Notion only if someone remembers to add it — which sometimes means never.
Atlas syncs contacts both ways, with full field mapping — not just a name and a number, but everything Google Contacts stores that can be matched to your Clients directory.
Just like Orbit, the setup runs on your own Google account — your contact data stays where it already lives, and Atlas just keeps it in sync with Notion.
The same "Duo" model as Orbit — adapted to the specifics of contact data.
Apps Script on your account checks every 15 minutes which contacts changed on either side since the last run.
Phone numbers, emails, address, company and custom fields — matched to the structure of your Clients database during setup.
Every run leaves a trace — more than 12 hours of silence signals that something needs a look.
The script and keys live with you — not on our infrastructure.
We match Google Contacts fields to the Clients structure you already have in Notion.
A manual fix won't be undone by the next sync run.
You can see the sync is alive — and know when it stops working.
You'll know what to do if you ever want to change something yourself.
Monthly monitoring and small mapping fixes — without a fresh setup from scratch.
Companies and freelancers who keep a client directory in Notion (e.g. in bāIMN), but new contacts still land on the phone first — and want the two to stop drifting apart.
This same contact-sync mechanism already runs across two accounts in bāAlpha's own daily operations — this isn't the first deployment of this model.
Priced higher than Orbit because contact-field mapping is typically more involved — phone numbers, emails, addresses and custom fields matched to your database, not just a name and a number.
Full contact data: name, phone numbers, email addresses, address, and custom fields matched to your Clients database — we agree the exact mapping during setup.
Atlas syncs, it doesn't clean up existing duplicates — that's a separate one-time step we can do before turning the sync on.
The script runs on your own Google account, keys are stored in its private settings — we don't retain ongoing access to your contacts once setup is complete.
Usually 3–5 business days — longer than Orbit, since client field mapping is typically more involved than task mapping.
Yes, we have experience running instances across several accounts at once — quoted as an extension of scope.
Not necessarily. Notion is our default choice — you can check it out yourself before paying. We also deploy for other systems, like Obsidian — tell us what you use and we'll match it.
Tell us what your Clients database looks like today — we reply within 2 business days.