Frequently asked questions

Yes. Setup happens through a conversation with Claude. It asks how your practice works, how you want information organised, what should stay private and which tools you use, then builds the structure around your answers.

There is no coding involved. If you are already comfortable using Claude and Notion, you should be comfortable setting this up.

Usually not.

Some company-managed Microsoft 365 or Google Workspace environments may require an administrator to approve a connection. That depends on your organisation’s security settings rather than on Tessentra itself.

Everything else is designed to be set up by the consultant using it.

Most of the work is done in one evening.

You install the system, answer the setup questions, connect the tools you want it to use and let it create the knowledge structure around your practice.

After that, it becomes more useful as meetings, decisions, commitments and client history accumulate.

A compatible Claude plan, a Notion account and access to the tools you want to connect — typically email, calendar, meeting transcripts and files.

The current compatibility requirements are listed in the documentation.

That’s fine.

Tessentra creates its own structured area inside your existing workspace. It does not need to replace the rest of the way you use Notion.

You can connect the tools your consulting work already lives in — including email, calendar, meeting transcripts, files and collaboration tools where supported.

Tessentra uses those connections to turn scattered information into structured client and project knowledge.

Not much. That is one of the main design principles.

You continue using your email, calendar, meeting tools, files and Claude. Tessentra connects and structures the information coming from those tools rather than asking you to maintain another system manually.

You will need to spend some time on the initial setup because that is where it learns how your practice works.

Immediately for tasks such as drafting, deliverables and structured workflows. The knowledge side becomes more valuable over time.

After your first meetings, emails and decisions are captured, Tessentra starts building context around your clients. As that history accumulates, briefs, proposals, reviews and other skills have more to work from.

A folder of documents gives Claude material to search.

Tessentra turns what happens across your practice into structured, connected knowledge.

A meeting can become a meeting record, several decisions, open commitments, stakeholder context and important dates — all linked to the right client and engagement.

That matters when you ask questions such as:

• Which commitments are still open?
• Who is actually influencing this decision?
• What changed since the last meeting?

Instead of repeatedly searching through documents and reconstructing the answer, those relationships are already part of the record.

Notion is an important part of the system. It is where the structured knowledge lives.

The difference is the consulting logic on top of it.

Tessentra determines what information means in the context of consulting work — whether something is a decision, commitment, open question, stakeholder insight or change in an engagement — and then gives that context to specialised skills that use it.

So Notion stores the knowledge. Tessentra structures it and puts it to work.

Claude’s built-in memory and Tessentra solve different problems.

Tessentra gives your practice an explicit, structured knowledge base that you control. You can inspect it, correct it, link information together, export it and decide what should be deleted.

More importantly, the skills work from that shared structure rather than relying only on what an AI system happens to remember from previous conversations.

Yes.

The underlying technologies are available to everyone.

What takes time is turning them into a system that works reliably across real consulting work: deciding how information should be structured, what context each task needs, how clients stay separated, how corrections persist, how updates are handled and which skills are actually useful.

That is the part we have spent months building, using and improving inside our own consulting practice.

Because the valuable part starts accumulating before the interface matters.

Your client knowledge lives in your own Notion workspace and the system is built around portable instruction and configuration files.

If the technology around it changes, you still retain the structured knowledge your practice has accumulated.

The context is the asset. The interface can change.

Yes. You can bring existing documents, meeting transcripts and other client material into the knowledge base.

Historical material needs to be interpreted and structured, whereas new information can be captured and organised as you work. For most practices, it makes sense to start with active engagements and bring older material in where it is genuinely useful.

Yes. The system is designed to be customised.

You can change your working rules, writing preferences, client structures and individual skills. You can also create additional skills around jobs that are specific to your practice.

Your practice-specific configuration is kept separate from the standard system wherever possible so updates do not simply overwrite the way you work.

Describe the job and Tessentra can help you build one.

Before adding it, the system can check whether an existing skill already covers the job so you do not gradually end up with multiple versions of the same thing.

That means the system can evolve with your practice rather than being limited to the skills it ships with.

It will sometimes get things wrong. It uses generative AI, and important outputs should always be reviewed.

The system is designed to make checking easier by keeping information connected to the underlying records and sources wherever possible.

Think of it as a well-briefed member of your team: much more useful because it knows the context, but still something you review before putting your name on important client work.

The system is designed to keep client records separate and to load the relevant client context for the task being performed.

That separation is part of the knowledge structure rather than something you have to remember every time you write a prompt.

Your structured client and project records stay in the Notion workspace you control. Claude processes information through your own Claude account when you use the system.

Fractal Force does not receive, store or have access to your client records as part of the product, setup or update process.

You remain responsible for deciding what client information your agreements and internal policies allow you to process through Claude, Notion and any other services you connect.

Yes. During setup, you define the rules for what the system may capture, what should stay private and what should never be recorded.

That matters when different clients have different confidentiality requirements. The system can reflect those rules, but you remain responsible for deciding what your client agreements allow.

No. Tessentra prepares the work; you stay in control.

It can draft an email, prepare a proposal, analyse a meeting or recommend a next step, but nothing client-facing is sent or published automatically.

You review it. You decide. You send it.

That can be a limitation.

If your client requires you to work entirely on a client-issued device or inside systems that cannot be connected to Claude or Notion, Tessentra may not have access to enough of the work to provide its full value.

If that describes your situation, talk to us before buying and we’ll tell you whether it is likely to work.

Yes.

One licence covers one company and up to five people, including employees, contractors and associates.

Everyone can work from the same shared client and project knowledge while using their own Claude account and their own connected tools.

How it works for teams →

Not currently.

Tessentra is designed for small, trusted teams where the people covered by the licence can work from the shared practice knowledge.

If you need client-level permissions, administrator roles or restricted access for particular associates, the current version is not designed for that.

Remove their access to the shared workspace and Tessentra from their Claude.

The client and project knowledge stays with the company. Their place within the five-user licence can then be assigned to someone else.

Those platforms evolve, and occasionally a change can affect part of the system.

We use Tessentra ourselves, so compatibility issues affect our own consulting practice too. Where an update is needed, fixes and compatibility improvements are included during your 12-month update period.

Your practice-specific settings and working rules are kept separately from the standard system wherever possible.

If you have directly changed a skill, you can compare your version with the updated version and decide which changes to keep.

The documentation walks you through that process.

Your licence does not expire.

You can continue using the version you have. What ends is access to new product updates and compatibility fixes.

Because Claude, Notion and other third-party services can change over time, continued compatibility with future versions of those services cannot be guaranteed without further updates.

Your licence and your copy of the product remain yours to use.

Your records remain in your own Notion workspace and your configuration remains under your control.

What you would no longer receive are future updates or compatibility fixes.

It stays with you.

Your structured records remain in your own Notion workspace, and the files and configuration you have installed remain under your control.

You are not building your consulting knowledge inside an account owned by Fractal Force.

Not currently.

The system is built around Claude and the way its skills and connected tools work.

If we add support for other AI platforms, we will document it rather than promise it before it exists.