1
The whole estate at a glance.
Which modules carry the estate, where the cells and the calculation time go, what feeds the board pack. The detail of any part when you want it. From the exports you already have, in minutes.
CodelessOps · Projects · Anaplan Architect
An architect who knows your estate.
Not just the build, but the project and design documents, the meeting notes, even your own notes. Ask it questions as an assistant to you. If you inherited a complex implementation, that replaces trawling through notes and a massive list of line items wondering why they are there. It runs on your machine. It is by no means the finished article, and I am looking for a few people to take it to the finish line.
01 · Three things it does
2
What a change would touch, before you make it.
Pick a line item. See everything it reaches, across models, down to the actions that export it. Put the count in the change request.
3
Why something was built the way it was.
Ask it. It answers from the exports, the project and design documents, the meeting notes, your own notes, and the conversations before yours. Every answer shows its source. The documents side is built on Grounded, my finance document engine, and is being joined to the Architect now.
02 · From the architect's seat
Everything it does, by the moment you would reach for it.
Each line says where it stands. Built runs today on the exports.Next is built on Grounded and being joined to the Architect.Backlog is not built and needs a live estate to build against.
A knowledge base you can ask
- builtEverything about the estate in one place: the exports, the documents, the notes, the conversations. Ask the most informed question you can and get the most informed answer, with the source shown.
- nextProject and design documents, meeting notes, change logs and your own notes, ingested next to the structure so the answer can cite the document that decided it.
- builtEvery answer points at an export row, a note or a document page. A claim naming something that does not exist is dropped before you see it.
When you inherit an estate
- builtThe whole estate on day one: which modules carry it, where the cells and the calculation time go, what feeds the board pack.
- builtThe spine first, then the reason the rest is there: the path between the spine and the outputs, and the modules nothing reads.
- builtWhy it was built the way it was, from the notes and conversations before yours.
When you change something
- builtThe blast radius before you touch it: everything a line item reaches, across models, through the imports, down to the export actions.
- builtA count you can put in the change request: line items, modules, exports, downstream models.
- builtIs it safe to delete: what reads it in the formulas, and what the notes say about who still relies on it outside the model.
- backlogWhich saved views and which actions use it, and which UX page it ends up on.
- builtA diff between two exports: what changed, where, and what it touched.
When you are asked if the model is any good
- builtForty-two checks against Anaplan's own checklist, each with the vendor wording, the object, why it matters and what to do. What is good gets reported too.
- builtA ranked fix list with evidence, grouped by effort: the roadmap input, with the reasons attached.
- builtWhy the model is the size it is: list, time and version sizes solved from the cell counts, each axis priced.
- backlogWhat changed, by whom, over years, from the model history.
When you are the one who knows things
- builtYour notes live with the estate, on any object, and are flagged when a later export changes what they describe.
- builtConversations are kept. The question a new joiner asked in March is still there in September, with the answer and its sources.
- backlogA model book regenerated from the export, one page per module, so documentation stays right without anyone maintaining it.
When you leave, or hand over
- builtThe estate keeps answering the reasonable questions. You get called for the hard ones.
- builtFor a consultant, a leave-behind the client keeps using, and a reason they call you for the next phase.
- backlogPull the exports through the Anaplan API on a schedule instead of by hand.
What it means for you, not the model
- You stop being the new person faster, because the first change request you write has the reach in it.
- You spend your time on judgment, which is what you are paid for, instead of reconstruction, which is not.
- You become the one who brought it in. The builder who can show the FD a dependency map and a ranked plan owns the estate rather than maintains it.
03 · Not finished
The exports do not hold these. Yet.
- Saved views and which action uses them.
- UX pages and what feeds each card.
- Model history.
These need a read-only capture from the model itself and a live estate to build against. I do not have one of my own right now. That is the reason for this page: I would rather build them with the people who will use them than guess.
04 · Beside CoPlanner and CoModeler, not against them
Anaplan put assistants inside the model. This one sits around it.
CoPlanner answers a planner's questions. CoModeler helps a builder change a model. The Architect reads every model at once, changes nothing, and keeps the reasons. Use CoModeler to build; use this to understand, onboard and hand over.
| For | Where | Does | |
|---|---|---|---|
| Anaplan CoPlanner | Planners | Inside Anaplan, on loaded data | Answers questions about the plan, raises workflow tasks. |
| Anaplan CoModeler | Model builders | Inside the modelling experience, one model | Builds and changes a model from natural language. |
| Anaplan Architect | Whoever inherits the estate | Outside the platform, on your machine, every model | An architect who knows the estate: build, documents, notes. Never changes a model. Cites the source for every answer. |
05 · Got 20 minutes?
I will show it running. You bring the three questions.
If you run Anaplan in-house, give me 20 minutes. I show it running on an example estate; you bring the three questions you would ask about yours. I built it on a very complex estate and it improved the confidence of my decisions and how fast I built. It is not the finished article, and I am not looking for a buyer. I am looking for a few people to take it to the finish line.
Built on anaplan-grammar andanaplan-estate, both open source. Part of my projects. Independent, not affiliated with or endorsed by Anaplan, Inc.; Anaplan is their trademark.
06 · Public record
What has been built.
Posts, walkthroughs and releases, each dated. Newest first.
07 · Questions
What are you asking me for?
Twenty minutes. I show it running on an example estate and you bring the three questions you would ask about yours. If you want to go further, one anonymised line items export and 45 minutes on your own estate. No pitch, no licence afterwards.
Does my model data leave my machine?
No. It runs locally. The assistant sends retrieved rows to the model provider you choose with your own key; without a key the rest works and nothing is sent anywhere. Cell data is never read.
How do I get an estate in?
Upload the line items, modules and actions exports from Model Settings. A pull through the Anaplan API with a workspace administrator login is the next piece being wired in; the API says less about where a model-to-model import comes from than the export does, so the export stays primary.
Does it use AI?
The assistant does, over facts that come from code: the parser, the graph, the checks. Every sentence it writes points at one of those facts, and a sentence that does not is dropped. The graph, checks, diff, size and plan are deterministic and need no model at all.
How is this different from the free estate review?
The review is one report from one upload. The Architect keeps the estate: snapshots, notes, conversations, diffs between versions, and an assistant that cites its sources. The review is the first look; the Architect is what you live in.
What does it cost?
There is no licence. A pilot is at my day rate and the tool stays with you. The grammar and the estate review underneath it are open source and free.
Is it finished?
No. What the screenshots show runs today; the documents side is built and being joined. Saved views, pages and history are not, and I need real estates to build them against. I do not have a live implementation to work on right now, which is why this page asks for your time and not your budget.