Sign up, connect HubSpot or Pipedrive or upload your files, and just ask. Columnly returns verified dashboards and briefs that stay live, re-sliceable, and refreshed daily โ inside a real multi-seat workspace, kept current by Autopilot.
Signing up creates your account, a fresh isolated organization, and makes you the Owner โ with a real per-org database provisioned before the account is even written, so a workspace is never half-created.
Enforced server-side on every request. Owners hold billing and ownership; members build, finalize and run Autopilot.
Single-use, email-locked, 7-day links. One email belongs to exactly one workspace โ enforced at send and at accept.
A master credit pool with per-seat grants. New teammates auto-get 500 credits; removing a member returns them to the pool.
Hand ownership to another member; remove someone and their sessions end instantly and their email frees for re-invite.
Everything starts from a single "Add source." Connectors are read-only forever โ a hard guarantee enforced by a positive scope allowlist at the provider edge. Columnly literally cannot write back to your CRM.
HubSpot: contacts, companies, deals, tickets, line items, products, custom objects, owners, pipeline stages โ and the real associations.
Pipedrive: Deals, Persons, Organizations, Activities, Products, Leads โ full custom fields and the links between them.
Both at once, namespaced so their overlapping "deals" and "products" never collide.
Each honest worksheet becomes a queryable source. Empty tabs, pivots and legend sheets are skipped, not mis-imported.
Honest type inference: a genuinely dirty column is kept verbatim as unknown, never silently coerced. Built for 500,000 rows ร 50 columns, streamed and stored as columnar Parquet in one verified commit.
It names what's wrong and quotes your own value back โ '1,000+', '58.6M', a 'Varies with device' sentinel.
A plain yes/no: "Clean it up" or "Use as-is." That sentinel becomes null, never 0.
Accepted cleaning is verified before it's applied โ if it can't be verified, it's refused, not shipped.
Frozen as a replayable recipe, so tomorrow's refresh re-applies the exact same decision.
Stays fresh automatically. Daily incremental refresh at 6 AM in your workspace's timezone. Failures retry, self-heal, then surface as an amber connection-health warning โ a broken pipeline is loud, never silent stale data.
amber > silenceEvery data question is solved twice โ one model decomposes and computes it, an independent model re-derives it from scratch โ and ships only when they agree. Before that, it decides which sources are actually relevant, and it discloses anything it had to leave out.
It decides which connected sources answer this question, anchors on one, and states a one-sentence reason for anything excluded.
A third check verifies the sources themselves were chosen correctly โ and only pauses to ask when getting it wrong would change the answer.
Aggregate โ a headline figure + method. Breakdown โ a table rendered deterministically from computed data. A task โ a confirmation.
On any dashboard or brief, every number is clickable. Click it and an anchored card shows Source โ Computation โ Reconciliation. Try it โ these are live:
This quarter you closed $4.82M in won revenue across 96 deals, at an average deal size of $50,208. Win rate held at 31% โ and Columnly flags that last one, because the open deals can't honestly be counted as either yet.
The green underline means proven before you even click. The amber dashed means honestly flagged โ never a silent wrong number.
A verified figure wears a green underline; an unreconciled one wears amber โ you can see which numbers are rock-solid without opening anything.
Before any artifact ships, automated verifiers confirm every figure cites a computed value and matches it, every chart's bars equal the stored series, and "highest/lowest" claims can't contradict their own chart.
If an insight can't be backed, it's dropped from the artifact โ not the whole board โ and you get three options, any alternative itself re-verified before it's offered.
The full mechanism โ the results store, server-owned figures, deterministic verification โ is on the trust page โ
An AI composes which components to show from a library of ~23 โ but it never states a number; a deterministic engine computes and verifies every value. So the composition is creative and the numbers stay bulletproof.
Filter the board and every figure recomputes and re-verifies over the slice โ live, in place, no reload. Try it in the console at the top of this page.
From a raw timestamp it derives time-of-day and day-of-week. It leads a scorecard with "delivered revenue," not a raw revenue that mixes booked and cancelled.
A second model adversarially grades every composition for weak stories and template-flatness, forcing a revision when it's weak.
Put a finalized analysis on Autopilot and it re-runs on a schedule against fresh data, no human in the loop. When you finalize, the analysis is snapshotted as an immutable record โ frozen recipes, locked lineage โ so it can't drift as rows change.
Pipeline broke โ loud "needs attention," last-good held. A soft figure โ quiet amber, still ships. A lie โ blocked entirely.
If the data hasn't actually changed, the run skips. Missed schedules collapse to a single catch-up run.
You pin the answers, figures and tables you care about; chat is never replayed โ only the frozen computation re-runs.
Grant a teammate viewer or editor access to a specific analysis; revoke anytime. Sharing is member-to-member inside your org โ there are no public, unauthenticated links. That's a deliberate trust posture.
Disconnect a CRM and you choose: reconnect, retain a frozen snapshot with a stale banner, or remove the data โ and even then artifacts survive as tombstones showing last-known figures. No disconnect choice ever makes a number silently disappear.
Sources show "Fresh" vs "static," an as-of date, and mixed-freshness is disclosed once. Snapshots are versioned with 15-day retention and atomic swaps โ a reader never sees a half-built refresh.
Each saved analysis holds multiple named chat threads, pins, and an inspector โ column stats on the left, threads in the center, the trace card on the right.
Free to start. Bring HubSpot, Pipedrive, or a spreadsheet โ and get answers you can actually defend.