By module
| Module | State | The specific gap |
|---|---|---|
| Accounting | Available | Commerce connectors are unfinished; no payroll, tax filing or inventory. |
| CRM | Available | Outbound SMS and voice are built and carrier-blocked. |
| Projects | Available | No time tracking or resource management. |
| Chat | Available | No voice, video, external guests or mobile app. |
| Phony | Available | Recording retention ceiling is stated and not enforced by a sweep. |
| Marketing | Available | No autonomous publishing, by design. |
| Client Portal | Available | Clients with no brand assigned can be routed wrongly. |
| PLM | In progress | Change control, quality and documents are not built at all. |
| Sign | Available | No identity verification; no configurable retention. |
| CFO | Available | No inter-company eliminations; tax views are partial. |
| Canvas | Available | No version history, no external guests. |
| Legal | Available | No citator — nothing tells you if a case is still good law. |
| Pey | In progress | Separate product. Match is in build; no customer-facing application. |
Built, deployed, and deliberately inert
These are the ones that cause trouble, because everything about them looks finished. The code exists, the screens render, the numbers move — and the thing does not actually happen.
| Thing | What works | What does not |
|---|---|---|
| Per-seat billing | Seat counting, the plan ladder, the trial gate, the meter. | Whether self-serve purchase completes depends on the payment rail being configured. Where it is not, plans say "Talk to us". |
| CRM outbound SMS and voice | The code paths, deployed and wired to a carrier. | The carrier account cannot place outbound calls or send SMS. Nothing goes out. |
| PLM change and quality sections | The navigation. | Everything else. The pages are placeholders. |
Because the alternative is somebody designing a workflow on top of one and discovering the gap after they have committed. A capability that is 95% built is more dangerous than one that is absent, because absence is obvious.
Things this product will never do
Not gaps — decisions. Listing them saves an evaluation that ends in disappointment.
- Cold outbound calling. Phony caps at callbacks, fast responses to verified forms, and existing-relationship calls. No list dialling, ever.
- Session replay and device fingerprinting. The agent works from what somebody tells it and from your published content, not from watching anonymous visitors.
- AI writing the ledger. Agents propose; people and deterministic rules post.
- MRP and shop-floor control. PLM describes what a product is; it does not plan production.
- Autonomous publishing. Every Marketing run is reviewed by a person.
About the screenshots on this site
Every product screen in these docs is drawn, not captured. They are vector illustrations built from the same design tokens as this page, and every figure in them is invented — no customer's data appears anywhere.
- The real screens are full of real books. A capture of the Accounting module is somebody's actual ledger, and this site is public and indexed. Redacting a hundred images by hand is a job nobody finishes correctly.
- This site has no raster images at all. It is hand-authored CSS and SVG throughout, and it follows the reader's light or dark theme. A screenshot taken in one theme is the one asset that can never follow the other.
- A capture is stale the day somebody moves a button. A drawing describes the shape of a screen — what is in the sidebar, what the columns are, what the row states look like — which is what a reader needs and which survives a visual refresh.
Screens that do not exist yet are drawn with a dashed frame and a "not built yet" stamp, so a placeholder cannot be mistaken for a feature. See PLM change control for an example.