What is not built yet

Everything on this page is absent on purpose or simply unfinished. It is collected here so that planning around the product does not require reading every page to work out what is missing.

Deliberately out of scope

Payroll calculation and filing

The handoff contract is the product decision rather than a gap. Being reconsidered — see Payroll.

Benefit claims

The product answers eligibility: who is covered, under what, from when. Adjudicating and paying claims is an insurance function with its own actors and regulator.

Recruitment

Different users, a different lifecycle, and adequate tools already exist.

Engagement surveys

Not the reason anybody switches to this.

Employer of record

Capital-intensive and legally heavy. A different business.

Currency conversion

Reporting is per currency and never converts. A rate and the date it applies on belong to finance.

Per-tenant data residency

Hosting is single-region and nothing in the product claims otherwise.

Modelled and reachable, but with no screen

Nothing. Everything the data model holds can now be entered and maintained from the interface — pay and allowances, pay requests, permits, benefits, terminations, cost centres, teams, boards and columns, and asset status. What remains below is unfinished detail inside features that exist, not whole surfaces missing.

Unfinished within features that exist

• No rich text in comments or descriptions — plain text with @-mentions, and attachments beside them.
• Search reads keys, titles, descriptions, comment bodies and attachment filenames. It does not read inside files — indexing arbitrary binaries is a parser surface to keep patched for a result nobody can preview.
• Time is recorded but not approved — a timesheet that argues with the person filling it in is one that stops being filled in. An expense is approved, because that one is a claim on money. Hours are priced, and what a contract says an hour is worth — a retainer, block hours, a cap — now decides the outcome too.
• Automation rules do not chain: a change made by a rule is not an event other rules see.
• No document upload form for checklist tasks that require one — the document must already exist.
• No bulk import anywhere, which is how a real inventory or an existing workforce actually arrives.
• No timer for time entries. Entries are recorded, not clocked — and a billing run does lock them once they are on a document.
• Board columns are edited as a list rather than dragged, and a board cannot yet be reordered by dragging its columns on the board itself.
• One language. The translation plumbing is in place, but shipping an untranslated locale that renders English is worse than not offering it.
• No mobile client, though every endpoint already serves one — see Mobile.

In the service desk

Tickets, the SLA clock, email in and out, the chat channel, the customer’s own view, leave-aware routing, satisfaction scoring, merging and canned replies, insights and the help centre all ship. What is left:

• No trend over time in [insights](/docs/service-desk-insights). Every figure is one period, and comparing two means opening the page twice. First-response time by week is the obvious next thing.
• Nothing offers a help article before somebody writes in. Articles are searchable and an agent can send one, but the chat widget and the hosted form do not suggest them — which is where deflection actually happens.
• The [help centre](/docs/service-desk-knowledge) reads a document folder and does not author articles, which is a decision rather than a gap. What it genuinely does not read is tables and images, dropped rather than approximated.
• No splitting a ticket that turns out to be two problems. Merging exists; the reverse does not, and it is a rarer thing to need.
• Time can be recorded against a ticket, but whether a contract already covers it is not answerable — retainers, block hours and included allowances belong to a professional-services module that does not exist.
• No change or problem management, no asset database, no call-centre routing.

In invoicing and the ledger

Sales invoices and bills, issuing and numbering, tax rates, bills captured from email, bank import and reconciliation, double entry, statements and the year end, fixed assets, consolidation and budgets, pricing work, what an hour costs, delivery and margin, sending and chasing, supplier payment runs, online payment, settlements and saved cards, the sync into Xero and Zoho Books and the month-end pack all ship. What is left is a short list of boundaries — things deliberately not done, each with a reason:

• Consolidation translates, but only from rates you type. Closing for the balance sheet, average for the profit and loss, the difference to a translation reserve. There is deliberately no market feed: a rate nobody chose is one nobody can defend, and an average is not computable from closing rates anyway. See the group.
• Your accountant’s books take documents out and give payments back, and nothing else. The chart of accounts, the tax rates, the bank feed and the ledger do not cross — two systems each keeping their own books and trying to agree is not an integration. A document raised in their books does not appear here.
• Minimum billing increments and fixed-fee phases are not modelled. Retainers, block hours, included allowances and caps all are — see contracts and allowances. Rounding every ticket up to fifteen minutes, and a fee split into phases that each earn separately, are two things a contract can say that nothing here reads. A product that guessed at either produces an invoice somebody has to apologise for.
• No open-banking consent flow. Reading an account as a third party needs a licensed provider and a qualified certificate, which is a company decision rather than a missing feature — and it is not needed: almost every bank connects on your own credentials or your own corporate agreement. See bank accounts.
• Saved cards work through Stripe only, because it is the one provider here that can charge a card later. Everywhere else a recurring invoice is sent rather than collected, which is never wrong — only manual.

In professional services

Charges, contracts and allowances, expenses, what an hour costs, delivery and margin, planning and utilisation and revenue recognition all ship. What is left:

• Nothing is billed automatically. A billing run is always a person looking at a preview and pressing a button. That is deliberate — nobody un-invoices two hundred hours — but it does mean an agency wanting invoices out on the first of the month has to raise them.
• Recognition posts when somebody posts it. There is no monthly job, on purpose: revenue moved between periods by a timer is indefensible whatever it computes. The consequence is that a month somebody forgets is a month that did not recognise.
• A plan does not see assigned work, and work does not see the plan. They are reported side by side and never summed, because they are the same hours described twice — but nothing reconciles them for you or warns when a plan and a backlog disagree.
• Cost rates convert only from rates you type. A margin whose cost is in another currency is withheld rather than converted at a guessed rate, and stays withheld until an exchange rate is supplied.
• Capacity planning has no scenario mode. You can see what is free, and you cannot model two competing jobs against each other without entering both.

In the CRM specifically

Contacts, companies, deals, activities, tasks, consent, proposals, mailbox and reply capture, text messages, HubSpot two-way sync, duplicate merging, import, custom properties, segments, email templates, pipeline reporting, click-to-dial with recording and transcription, forms, booking links, the chat widget, messaging handles and the suppression list all ship. What is left:

• No sequences. Automated multi-step outreach is worth nothing before consent tracking governs it, which it now does — so this is next rather than absent on principle.
• No lead scoring. Scoring is worth nothing before there is history to score against, and a fresh tenant has none.
• Booking links create a video meeting but still do not READ a calendar. Teams, Meet and Zoom links are made per booking, but a meeting somebody accepted in Outlook does not block a slot — only leave, holidays and bookings made here are known.
• The [chat widget](/docs/crm-chat) has no presence and no typing indicator, and nothing emails you when a message arrives. Both are deliberate — there is no signal here that would make an online badge true — but they are what somebody expects and does not get.
• Email is one-to-one, plain text, no attachments, and carries no tracking pixel — that last one is a decision rather than a gap.
• Proposals carry no priced line items. A quote with lines, tax and totals belongs to invoicing, and two pricing engines is how two systems disagree about what a client owes.