CoNote
The company logbook

Your traffic dropped on March 14. CoNote knows why.

Every deploy, campaign, and config change — one shared timeline your whole team can read. When a metric moves, the cause is already on the page.

Start your logbook — freeSee how it works

Keeping their logbook with CoNote

  • Northwind
  • Meridian
  • Beacon
  • Vela
  • Lumen
  • Cardinal
#revenueMonday
MK

Mia09:12

Conversion is down 18% since last Tuesday. What changed??
TB

Tom09:14

Nothing shipped on our side… I think?
SR

Sara09:21

Wasn’t the agency in Tag Manager recently?
TB

Tom09:24

Maybe? That was like three weeks ago. Does anyone have notes?

Nobody has notes.

Monday, 09:12

Conversion is down 18%. Marketing has no idea what changed.

So the archaeology begins: grep Slack, ask around, try to remember who touched what. Sound familiar?

The answer was never missing.
It just wasn’t written down anywhere.

How it works

Three steps. Then it runs itself.

  1. 01

    Connect your tools

    No SDK, no engineering sprint. Each source connects the way you’d hope — paste a URL, click authorize, or drop in a file. Your logbook is collecting within minutes.

    • GitHub: paste a webhook URL into the repo settings
    • Tag Manager: a two-click Google authorization
    • Your history: import a CSV from Jira, Asana, or any spreadsheet

    Connected sources

    GitHub

    conote.io/api/hooks/x7f2…

    Connected

    Google Tag Manager

    Authorized with Google

    Connected
    CSV

    jira-export.csv

    1,204 rows mapped

    Imported

    Each source takes minutes — and counts as one seat.

  2. 02

    Events log themselves

    From then on the timeline writes itself. Every deploy, budget change, config edit, and error spike lands the moment it happens — stamped, categorized, and attributed to its source.

    • Readable titles: “Deployed storefront v2.4.0”, not “push event received”
    • Seven categories keep every department on the same page
    • Manual notes catch the rest: decisions, pricing changes, agency work

    Acme · Timeline

    Error spike: checkout timeouts (214 events/h)

    SentryWed 08:47

    GTM container v45 published — checkout tracking changed

    Tag ManagerTue 11:05

    Spring sale — daily budget raised to $450

    Google AdsMon 15:12

    Deployed storefront v2.4.0 (main → 3a7f2c1)

    GitHubMon 09:41

    Four departments, zero manual logging.

  3. 03

    Find the cause

    When a metric moves, you don’t schedule a meeting — you open the timeline at that date. Every change from every team is on one page, so the outlier is usually obvious.

    • Scan the days around the shift on one shared page
    • Filter by category and source, or search the logbook
    • The answer is a date and a name — not a guess

    Acme · Logbook

    Mar 14· 3 changes that week

    Deployed storefront v2.3.9 (main → 91be4d0)

    GitHubMar 13, 16:20

    GTM container v45 published — checkout tracking changed

    Tag ManagerMar 14, 11:05

    Found it

    Spring sale — daily budget raised to $450

    Google AdsMar 15, 09:30

    Every team’s changes around the date, on one page.

Integrations

Every team’s tools, one timeline.

Deploys from GitHub, container versions from Tag Manager, budget changes from Google Ads — sources from every department write into the same logbook. Anything not listed can write in through the webhook.

  • GitHub
  • Google Tag Manager
  • Webhook
  • Google Algorithm Updates
  • Uptime
  • Weather
  • Site Watch
  • Vercelsoon
  • Netlifysoon
  • GitLabsoon
  • Bitbucketsoon
  • Jirasoon
  • Google Adssoon
  • Meta Adssoon
  • Mailchimpsoon
  • HubSpotsoon
  • LinkedIn Adssoon
  • TikTok Adssoon
  • X Adssoon
  • Shopifysoon
  • WooCommercesoon
  • Stripesoon
  • LaunchDarklysoon
  • Sentrysoon
  • PagerDutysoon
  • Google Search Consolesoon
  • WordPresssoon
  • Contentfulsoon
  • Webflowsoon
  • Slacksoon
  • Microsoft Teamssoon

7 live today · 24 rolling out

Browse all integrations

The payoff

When the number moves, the cause is one glance away.

Put your metric next to the timeline. The dip on March 14? Two things changed that day — and one of them touched checkout tracking.

Conversion rate

Mar 1 – Mar 20

−18%

Same day on the timeline

GTM container v45 published — checkout tracking changed

Configuration · 14:17

likely cause

Spring sale — daily budget raised to $450

Campaign · 11:02

CSV

jira-export.csv

1,204 rows

SummaryTitle
ResolvedEvent date
Issue typeCategory

Columns auto-detected — review, click import, done.

BRING YOUR HISTORY

Three years of history, on the timeline this afternoon.

Export from Jira, Asana, or any spreadsheet. Map three columns — title, date, category — and the import wizard does the rest. Your logbook starts full, not empty.

WHY THIS EXISTS

As a consultant, I kept asking clients the same question — “your traffic moved in March last year; what changed?” — and kept getting the same answer: nobody remembers. The deploy log knew. The ad account knew. Tag Manager knew. But no single place knew everything, so every metric dip turned into archaeology.

I always wished my clients had simply kept a record of what they shipped, spent, and changed. No tool made that effortless — so I built one.

Think of it like insurance. The day a number moves, the answer is already on the page. The day nothing breaks, you’ve lost nothing keeping it. A logbook only works if writing in it is free — so connect your tools once, and the record keeps itself.

— Stefan, founder

Security & privacy

Your logbook is yours.

CoNote holds your company’s history, so we treat it that way:

Read the privacy policy →

PRICING

Priced by team, not by surprise.

A seat is a team member or an active integration — both do the same job: they write in your logbook. That's the whole pricing model.

Free

$0/mo

 

For trying out the logbook.

2 seats · 100 notes

  • · Timeline and logbook
  • · Manual notes
  • · CSV import
  • · 1 member + 1 integration
Start free

Basic

Most teams

$25/mo

$300 billed yearly — save $60

For small teams getting a shared record.

3 seats · 1,000 notes

  • · Everything in Free
  • · All integrations
  • · Team invitations
  • · Ingestion API access
Start with Basic

Pro

$70/mo

$840 billed yearly — save $168

For teams that live in the logbook.

10 seats · Unlimited notes

  • · Everything in Basic
  • · Unlimited history
  • · Priority support
Start with Pro

Enterprise

Custom

 

For large organizations with custom needs.

Unlimited seats · Unlimited notes

  • · Everything in Pro
  • · Custom integrations
  • · Contract & invoicing options
Talk to us

Paid plans are billed through Stripe. Upgrades apply immediately; downgrades never delete data.

QUESTIONS

The fine print, in plain language.

Each team member and each active integration counts as one seat. The Free plan has 1 seat, Basic has 3, Pro has 10. Pausing an integration frees its seat.

No — that’s the point. Connecting GitHub is pasting a URL into the repo settings. Tag Manager is a two-click Google authorization. The CSV import is drag, map, done.

New entries are blocked until you upgrade — existing notes are never deleted. Your history stays intact on every plan.

Yes. The CSV importer accepts exports from any tool. The column mapper auto-detects title, date, category, and details headers, and shows a preview before anything is written.

Your logbook is visible only to your team. Deleting your account removes the team and all of its data permanently — there is no soft delete.

Yes. Create a team-scoped API key in Settings and POST events to /api/v1/ingest — single events or batches of up to 100, with deduplication via external ids.

Open the logbook.

Free plan, no card. The next time someone asks "what changed?", the answer is one search away.

Start your logbook