DDocuments + deadlinesActive
A client portal for accountants that every client reads their own way.
A bookkeeping client wants to see open invoices. A tax client wants documents and deadlines. A CFO-style client wants statements and cash position. Same firm, same data model, very different needs. ShapeKit lets you build one portal and lets each client reshape their own view of their statements, documents, and tasks, inside the limits you set.
The problem
You serve a range of clients with one practice, but they do not want to see their numbers the same way. So you end up sending different reports, maintaining different spreadsheets, or asking your developer for yet another portal variant. Every tax season the requests pile up, and none of them are about the accounting. They are about the layout.
Every client reads differently. One wants a running list of documents to sign. Another wants a clean statement summary. A third wants tasks and due dates up front. You cannot pre-build all of it.
The data is sensitive. Financial records cannot leak between clients. A flexible portal that puts isolation at risk is worse than a rigid one.
Deadlines do not wait for a release. A client asks for a different view mid-season and you do not have a week to ship it.
How ShapeKit solves it
Build one portal with everything a client might need: statements, documents, tasks, deadlines, and messages. Each client logs in and sees a Shape button. They describe the view they want and the AI rebuilds it. Documents first. Open tasks grouped by due date. Statements as a summary instead of a ledger. You set the limits; they arrange the rest.
Build the practice portal once
Define statements, documents, tasks, and deadlines, with permissions per client. No need to anticipate every client's preferred layout.
Clients shape their own view
Each client reshapes what they see by asking for it. Hide what they do not use, surface what they check weekly, group it their way.
Their data stays their data
Isolation is enforced server-side. A client can rearrange their own view all day and never see another client's records.
One app, no per-client rebuilds
You stop maintaining a stack of near-identical portals. When you update the base app, each client's shape is versioned and migrates forward, so a change to your statement layout does not break the view a client set up last quarter. One portal to maintain, a personalized view for every client.
Give every client the view they want, on data you keep locked down.
Build one accounting portal. Let your clients shape it. Keep their records isolated.