Skip to content

Evidence inventory · 25 July 2026

What ships today

Every capability you can use today, and every verified gap, across five stages of client work.

5

stages

239

public capability statements

50

verified gaps named

A capability appears under Ships today only when a person can reach it end to end. Engines without a surface, placeholders and broken paths appear under Not built.

1.0

Win

Find, clean and qualify the work worth winning.

92 live statements7 verified gaps

Full inventory

  • Contacts and acquisition11 live
  • Filters, segments and export15 live
  • Record depth and enrichment16 live
  • Outreach25 live
  • Opportunity decisions10 live
  • Upwork assistant15 live

Verified boundary

Not built

No roadmap date implied. No placeholder counted as product.

  • Taoro does not ingest anonymous visitor intent, identify visitors by IP, or buy firmographic and technographic feeds.
  • Standalone opportunities cannot be attached to contact records, so Taoro is not a connected sales pipeline CRM.
  • Contacts use a fixed set of structured fields; users cannot create arbitrary custom contact fields.
  • The lead mobile API has no shipped mobile client.
  • The campaign Workflow tab contains placeholder steps, and Taoro has no native outreach sequence builder; cadence lives in Instantly.
  • The reply feed is email only and read only; it cannot compose replies or combine LinkedIn and SMS conversations.
  • The probability model does not derive a new opportunity’s prior from historical outcomes in its segment.

2.0

Book

Let clients book real time, on your domain.

44 live statements11 verified gaps

Client facing doors

Client door 01 · Book

The client's view

/book/[orgSlug]/[typeSlug]

The public surface a client opens.

The boundary

Guests pick a time and land on your calendar.

They cannot cancel or reschedule themselves yet.

Underneath this

  1. 01Weekly rules plus date overrides, buffers, notice and advance cap.
  2. 02DST correct slot math in two passes.
  3. 03HMAC signed slot tickets stop a guest from forging a start time.

Full inventory

  • Event types and availability18 live
  • Calendar and public flow9 live
  • Notifications and staff operations7 live
  • Branding, domains and embeds10 live

Verified boundary

Not built

No roadmap date implied. No placeholder counted as product.

  • The stored event type host roster does not route bookings, and round robin or assigned host booking does not exist.
  • Public booking submissions are screened by a honeypot and Turnstile, but they are not rate limited.
  • The confirmation page self cancel link currently leads to a route that does not exist.
  • Guests cannot reschedule themselves; rescheduling requires authorized staff.
  • Paid bookings and deposits do not exist.
  • Group and multi seat events do not exist.
  • Google Meet is the only native conferencing option; Zoom and Teams are not connected.
  • Booking reminders are email only; SMS reminders do not exist.
  • Recurring bookings do not exist.
  • The active event type counter has no visible consumer or plan limit surface.
  • Public booking pages do not yet ship the claimed “Powered by Taoro” badge or viral loop.

3.0

Run

Model the work, then let rules move it.

49 live statements6 verified gaps

Client facing doors

Client door 01 · Brief

The client's view

/f/[token]

The public surface a client opens.

The boundary

A client submits a brief and it lands as a task on the right board.

They cannot attach files yet.

Underneath this

  1. 01Dropdown options read the board’s current columns, never a snapshot.
  2. 02The submission becomes a task with your fields.
  3. 03The team is emailed within seconds.

Client door 02 · Watch

The client's view

/share/[token]

The public surface a client opens.

The boundary

Clients see the columns you chose and nothing else.

They cannot comment or approve yet.

Underneath this

  1. 01Eight structural fields can never appear, whatever you select.
  2. 02Every link is revocable.
  3. 03Public views support light and dark on your brand.

Full inventory

  • Board model6 live
  • Views6 live
  • Task detail and collaboration9 live
  • Files and custody7 live
  • Client facing work8 live
  • Templates and handoffs8 live
  • Automation5 live

Verified boundary

Not built

No roadmap date implied. No placeholder counted as product.

  • My Work, Dashboard and Workload inside the view switcher are placeholder tabs; the real cross board page is /tasks/overview.
  • Comments store correctly, but comments and mentions do not notify anyone.
  • The automation notify action records intent but does not deliver a message to a person.
  • Assignment change, cell change and date reached triggers are selectable but have no producer and will not fire.
  • Clients cannot comment or approve from a shared board.
  • Clients cannot attach files to an intake form.

4.0

Bill

Invoice, chase and reconcile without a second tool.

32 live statements18 verified gaps

Client facing doors

Client door 01 · Pay

The client's view

/pay/[token]

The public surface a client opens.

The boundary

A client pays by card and the invoice settles itself.

The invoice is a web page, not a PDF.

Underneath this

  1. 01Double entry posts on issue and reverses on void.
  2. 02EU reverse charge and compound VAT use live ECB rates you can override.
  3. 03Card payment runs through your own Stripe account; the money never touches ours.

Full inventory

  • Ledger and reports5 live
  • Invoices, payments and collections14 live
  • Clients and reconciliation8 live
  • Time to invoice5 live

Verified boundary

Not built

No roadmap date implied. No placeholder counted as product.

  • The general ledger engine exists, but there is no general ledger viewer.
  • Users cannot create custom ledger accounts through an action or page.
  • There is no balance sheet report.
  • There is no invoice PDF.
  • Issuing an invoice does not email it; only overdue reminders send automatically.
  • There are no accounts payable, vendors or vendor bills.
  • There is no expense tracking model or surface.
  • Bank import is pasted CSV only; there is no bank connection, file upload or OFX, MT940 or CAMT.053 parser.
  • Board hour columns do not become invoice lines; invoiced time must come from a connected time provider.
  • A fresh organization is not given its default chart of accounts automatically.
  • Nobody can subscribe to or pay Taoro in product today.
  • There is no billing settings page for plans, seats or Taoro invoices.
  • The plan catalog exists only in the database and no application code reads it.
  • A new organization does not receive a usable billing profile automatically.
  • Billing domain events are recorded, but no consumer acts on them.
  • Seat changes exist only as an unused database table.
  • Plans do not drive feature entitlements, so tier boundaries are not enforced product truth.
  • The Stripe subscription webhook receiver works, but it is only the receiving half and does not create a subscription path.

5.0

Govern

Decide who can do what, and with whose keys.

22 live statements8 verified gaps

Full inventory

  • Access and organization8 live
  • Authentication6 live
  • Keys, integrations and controls8 live

Verified boundary

Not built

No roadmap date implied. No placeholder counted as product.

  • Email and password signup currently fails in production; Google OAuth and magic link access work.
  • There is a notifications page, but there is no global notification bell or unread badge in the app shell.
  • Organizations cannot enter their own Instantly credentials because the cold email provider has no settings card.
  • Tier preset machinery is unreachable, and its paid tier branches currently skip rather than provision features.
  • Background pipelines are scheduled, not real time; their intervals range from five minutes to daily.
  • There is no whole workspace data export; only narrower exports such as the contact export are evidenced.
  • The standalone jobs module has no customer surface and is only an outbox test harness.
  • Share links do not hide every potentially sensitive user defined value by default; the organization chooses visible columns, while only the eight structural exclusions are absolute.