About · Building for launch customers

A small team, building the analytics layer we always wanted to use.

We started Arcus because operators keep describing the same morning: open the warehouse, ask for context, check a dashboard, copy a chart into a memo, then do it again tomorrow. Arcus is built to turn that loop into an answer with the work shown.

Status: Launch readiness
Focus: Executive intelligence
v1: Warehouse-first
Sources: BigQuery · Snowflake · Postgres
Stage: Early. Building.

The story

How we got here.

Arcus exists for the executive question that never fits cleanly in a dashboard: "why did this number move, what changed underneath it, and what should we do next?"

The product is intentionally narrow for v1. It connects to a tenant's warehouse with read-only access, uses the tenant's semantic configuration, validates generated SQL before execution, and returns the three layers every answer needs: narrative, visualization, and raw data.

We are preparing Arcus for launch customers, not claiming broad public traction. Public customer logos, production case studies, funding announcements, and headcount numbers will only appear here after they are approved.

"The promise is simple: ask the business question, see the reasoning trail, inspect the rows, and leave with a decision."— Arcus product principle

Today, Arcus is built for founders, finance leads, growth leads, and analytics partners who need answers with the work shown. We're small, focused, and still just getting started.

A short history

The launch plan in six moments.

Warehouse-first scope.

v1 centers on BigQuery, Snowflake, and Postgres rather than direct SaaS connectors.

Tenant semantic layer

Each customer defines business terms, metrics, and source mappings separately.

Guarded agent tools

The LLM controls the loop; server tools enforce validation, budgets, and tenant scope.

Three-layer answers

Every complete response returns narrative, visualization, and raw data together.

Security review

SOC 2 is in progress; current security materials are available by request.

Launch pilots

Qualified teams can request a guided setup and production-readiness review.

The team.

Mode

Focused

Scope

Public logos

0 approved

Hiring

Interest list

Product strategy

Executive workflows, pilot scope, customer discovery

Launch function

Agent engineering

Tool loop, budgets, traces, model orchestration

Launch function

Experience design

Threads, artifacts, dashboards, and launch pages

Launch function

Platform engineering

Multi-tenant app shell, auth, APIs, observability

Launch function

Go-to-market readiness

Contact flows, pricing scope, launch-safe claims

Launch function

Semantic layer

Tenant metrics, warehouse metadata, schema mapping

Launch function

Data connectors

BigQuery, Snowflake, Postgres, and read-only setup

Launch function

Security posture

Secrets, tenant isolation, SQL validation, review packet

Launch function

Customer setup

Guided pilots, source scoping, readiness checks

Launch function

Evaluation quality

Gold questions, answer contracts, regression review

Launch function

Operations readiness

Support, procurement, legal packet coordination

Launch function

Want to be next?

Join the interest list →

Interest list

Operating posture

Built for the trust bar executives expect.

We do not publish investor, funding, or advisor claims until they are approved for public use. For launch, this page focuses on product posture and scope.

Warehouse firstv1 scopeBigQuery, Snowflake, and Postgres

Tenant scopedarchitectureevery request and query includes tenant context

Guarded toolsagent harnessvalidate before execute, with budget and trace controls

Honest trustlaunch postureSOC 2 is in progress, not claimed complete

Public proof policy

Customer logos, named advisors, funding details, certifications, and benchmark numbers need explicit owner and legal approval before they appear on the public site.

Principles

Six things we hold with conviction.

An answer, not a chart.

The unit of value is "I now know what to do." A chart you have to interpret is one step short of that. We'll keep optimizing for the answer, not the artifact around it.

ii.

Show the work.

An answer without provenance is a guess in a nicer outfit. Every Arcus answer shows the data, the SQL, the assumptions, and the things it skipped — by default.

iii.

Slow is fast.

We'd rather ship one feature that lasts five years than ten that last five months. We say no to most things, including most product ideas. Especially the loud ones.

iv.

The operator is the customer.

Our customer is the person who has to make the decision tomorrow. Not the buyer, not the IT team, not the platform. We optimize the experience for the person doing the work.

Trust is earned daily.

We will, occasionally, get something wrong. When we do, we'll say so, fix it, and explain. We don't believe in vague status pages or "incidents" that magically self-resolve.

vi.

Make it boring to use.

If a feature surprises you in a bad way, it's a bug, not a feature. We want Arcus to be the most dependable software you use this decade — quiet, predictable, fast.

Where we work

Remote-first. Customer-close.

Product

Launch team

Product, design, and engineering collaborate remotely with customer-facing setup calls by calendar.

Scope

Warehouses

Remote

Mode

Security

Review path

Qualified prospects can request the current security overview, DPA draft, and architecture packet.

SOC 2

In progress

Read

Access

NDA

Packet

Support

Customer setup

Launch pilots are handled directly so source coverage, credentials, and success criteria are clear.

Guided

Setup

First

Pilot

Ready

Want to work with us?

We're not actively hiring right now. Join the interest list and we'll reach out when roles open.

Join interest list Get in touch