● the workshop

90 minutes with your
leadership team.

we map your sources, your AI usage, and the three queries that would move the needle most. you walk out with a scope and a written plan within 48 hours.

hey@theblankcollar.com
engagement

how an engagement
actually runs.

01
week 1
discovery
90 min workshop with your leadership. we map sources, usage, priority queries. you walk out with scope and plan.
02
weeks 1–3
build
infrastructure live in days. first sources ingested. entity taxonomy designed for your business. skills configured.
03
weeks 3–6
adopt
role-specific training. daily briefings wired into slack. 30 day embedded support. adoption curves managed.
04
ongoing
expand
new sources on cadence. new skills as workflows emerge. quarterly strategy review. blankcollar compounds.
tiers

three ways to start.

for founders and small teams

starter

talk to us
scoped after discovery
  • · core knowledge layer
  • · 1-2 sources connected
  • · priority query workflows
  • · onboarding support
most chosen
for companies rolling out across teams

growth

talk to us
scoped after discovery
  • · everything in starter
  • · up to 5 custom connectors
  • · team training across functions
  • · daily briefing config
  • · priority retainer support
for regulated industries and complex orgs

enterprise

talk to us
scoped after discovery
  • · everything in growth
  • · on-premise deployment
  • · sso and rbac
  • · audit logging
  • · dedicated delivery lead
faq

commercial & strategic.

why don't you publish prices?

every engagement depends on your sources, your team size, and your compliance requirements. we scope precisely after discovery. you get a fixed price in writing within 48 hours of the workshop. no surprises.

what if openai, google, or anthropic build this?

they will build a version. it will be us-hosted, locked to their model, and generic. that's the right product for many companies. if you need sovereignty, provider independence, industry depth, and a team that knows you, you need something different.

what happens to our knowledge if we leave?

you own it. the knowledge layer is yours from day one — markdown repo, database exports, and skills all in your control. leaving is a config change. your knowledge travels with you regardless of the decision.