Updates

Since the beginning of building Republik, the prospect's problems have always been the center point. It is the single most useful thing to build an approach on because it is what connects you with your future customers.

We have called this the problem anchor. But today we shift that thinking. The playbooks have always been very confident in how it reads the account signals and then picks the core problem while showing you the other problems as well.

Sometimes the problem is evident from public signals, but most times it was not as certain as Legatus let on. It was stated on facts inside companies we could not see, and lack of evidence was treated as a gap at the account, not in the research.

So it could confidently guess wrong.

Today we introduce the replacement: The problem hypothesis

Legatus 1.2 changes the posture. It no longer tells you what the problem is. It tells you what the problem most likely is and shows its work.

The language is softer on purpose. "They have this problem" becomes "this is most likely their core challenge."

Every hypothesis is built the same way:

• —

  What the company visibly does. Its hires, its moves, its own words.

• —

  Where that most likely breaks. The pain those facts point to.

• —

  What we can't see from outside. Said plainly.

• —

  The question that tests it. One question for the first conversation.

When public signals point straight at the problem, the facts carry the hypothesis. A funding round, an expansion, open roles and leadership churn add up to one likely challenge. You see every step.

When the signals are thin

Some accounts show the problem in public. Others only show the conditions for one. A certification. A Trust Center. A deadline on the horizon.

Before, Legatus filled that gap with a guess. Now it reaches for a pattern. What usually breaks at companies in this situation. And it labels it clearly as a pattern.

The pattern comes from your agent training. A study, a benchmark or a case from your content library. So your own material does the work.

Same method every time. Where the problem shows, the hypothesis rests on those facts. Where only the conditions show, a pattern bridges the gap. Either way, the rep knows how sure the playbook is. And can still say it out loud.

What you see

• —

  Why this account reads as a short story. What is happening, the likely pain, the signals. It ends on one line: Problem hypothesis.

• —

  The Core challenge card on the Brief carries that same line. Word for word.

• —

  Intelligence holds the longer argument. What the company does today, the most likely break, what we cannot see and the question that tests it.

• —

  The approach opens with that question.

When the research could not find something, the playbook says it is not visible. Never that it is missing.

You have access to it now. It takes effect on each account's next playbook. Existing playbooks stay as they are.

Also shipped

An account playbook is only worth something if the data under it is right.

Legatus runs on the same models you open in ChatGPT or Claude. The difference is what it was built to do. ChatGPT is built to answer anything. Legatus is built for one job: research an account and turn it into a strategy. It knows what a company size is supposed to mean, which financial year counts, and what makes an angle worth opening with. Ask an AI to size a company and it hands you whatever it finds first, often one registered entity in one country, because nothing told it that was the wrong answer.

We tell it. Since launch we have run 100s of real account playbooks, used to open and win real accounts. At the start of September we read back through them and found every place the agent had read a fact loosely, reached for the wrong source, or built a case on a number that was no longer the newest one.

Today we ship Legatus 1.1. Twenty six of those corrections, on every playbook you build from here.

Here is what changed on the page you actually read.

Old financial numbers can no longer carry an argument. A playbook reaches for financial data to build the strategy. Maybe a company missed its own expectations. Maybe it is growing fast. Maybe the numbers make the case that now is the moment to reach out.

The research turns up several numbers, and sometimes the argument got built on the older one. It pulled from 2024 or 2023 when the 2025 annual report was sitting right there. So you send a case about a weak year to a company that has since published a strong one, and they stop reading.

The new rule: a number published more than a year ago can never carry an argument. It can only give a sense of direction. Everything you see carrying weight on a playbook is from the past year.

Company size now describes the company, not one piece of it. A playbook uses size to work out who you are approaching. A 300 person company and a 3,000 person group are different sales.

The research took size from whichever source it found first, often a national business registry. A registry only counts the entity registered in that country. So a global brand with 1,000s of employees came back as a few 100, and the strategy was written for a company that size.

The new rule: annual report first, the company's own site next, registry last.

Now the size on a playbook is the size of the business you are selling to.

Every source link opens the page the fact came from. A playbook makes claims about a company. When one matters, you click the source to see it for yourself.

About 1 link in 16 opened the company's front page instead. The research knew where the fact came from but never wrote the address down, so the playbook made one up. You clicked a claim about a hiring plan and landed on a homepage.

The new rule: the agent keeps every page it opens and cites the fact against that page. A link the research never carried does not get written.

Now every link goes where it says it goes.

The playbook thinks before it writes. Legatus works out plenty about an account before it builds the strategy. What to lead with. Who to open with. And what to stay away from, like a sore point or an angle the company is tired of hearing.

It only worked out what to avoid after the case was already written. So the avoid list came too late to shape anything.

The new rule: everything Legatus knows about the account goes in before the case gets built, not after.

Now the strategy is built on the full picture, and the case holds together with the advice around it.

You can see which sources Legatus could not read. Your Research Guide tells Legatus where to look. Industry sites, registries, wherever you know the good information sits on your accounts.

Some of those sites never open. A few block automated readers on purpose. Others sit behind a login, or a cookie wall, or answer so slowly that the request times out. You had no way of knowing, so a source you were counting on could be missing from every account and the research would look complete.

The new rule: if we try a site several times and never get an answer, we tell you it is not reaching your account research, so you can swap it for one that does. Leave it in if you want. We retry every blocked source once a month to see if it lets us in.

Now you know which of your sources made it in.

In August we taught Legatus to say when it could not confirm a role. Honest, but it left the work with you. A person marked "verify first" still had to be verified by someone.

Now Legatus does the checking.

Every person passes a verification step. After research, Legatus looks for current, dated public evidence that each person still holds the role. It marks them Confirmed, Probably departed or Unknown, and shows you what it found.

Departed people leave the Playbook. Someone who has moved on is taken off the roster. They appear once on the Intelligence tab under Probably departed, with a was → now line, the date and the corroborating sources. Strategy never recommends contacting them. It flags the vacated role instead.

Confirmed people carry a date. A verified person reads "Confirmed on LinkedIn 8 Sep 2026", so you know when it was last checked. A roster title that looked stale is upgraded when the live evidence agrees.

Missing profile links get filled in. When name and company match cleanly, the link is added with the source cited.

Fewer "verify first" warnings. The August rule still stands, but it now only fires on people Legatus could not settle either way.

Accounts you have already built show the new format without a rebuild.

Financials now rest on the latest filed year

Revenue and result in research and strategy come from the most recent filed accounts, named with year and level (group or legal entity). Older years show as direction only, never as a standalone number or a news item. Multi-year criteria like "declining revenue two years running" are judged on the latest filed years. Known limit: company registers answer intermittently, so a failed lookup is held back as Unknown rather than replaced by an old figure.

Your account playbooks now work inside the AI you already use. Connect Republik to Claude, ChatGPT or any other tool that supports MCP, and it can see your whole account list and pull the full playbook on whichever accounts your question needs.

The intelligence then sits in the same conversation as your CRM, your inbox and your calendar. Ask about an account and you get both sides. Your relationship with them, and what is happening at their end.

Five things your AI can read

• —

  List accounts. Every account in your workspace, with fit, segment and how fresh the research is

• —

  Get account brief. The account story, the people and their role in the decision, why this account, why now, why us

• —

  Get approach. The play, the first move, per-person angles, talking points, objections

• —

  Get signals. What research surfaced on timing, hiring and news

• —

  Get content. Your saved outreach drafts, one per person and angle

See more examples on how to use these functions in the product launch post.

Two ways to connect

Connect by URL. Paste app.runrepublik.com/api/mcp into your AI tool's connector dialog. Then a sign-in form will open and you sign in to Republik the way you normally do, and you can start using your Account Playbooks inside your AI.

You can also connect with a key. Create one under Settings, paste it into any tool that expects a key.

It reads only, either way. Your AI cannot generate, change or delete anything. Settings lists every app you have connected and every key you have created, so you can disconnect an app or revoke a key at any point. Access stops immediately.

Step by step setup for each tool is here: Connect Republik to your AI tools.

When you anchor a strategy on a specific person, you want to be sure it's the right person.

We found examples of people who were no longer at the company still showing up in playbooks, because the evidence of them leaving was never there. That's common practice: companies announce who they hire, not who left.

In one case, Legatus listed a Head of Marketing as the person to approach at an account, and the whole strategy pointed at her. She had left the company eight months earlier. Three separate directories still showed her in the role, none of them dated, and she had changed her surname, so a search on her old name and the company turned up nothing to contradict them.

Legatus now treats an undated directory listing as identification, not as proof that someone still holds the job. To call a role current it needs a live profile, a dated mention from the last twelve months, or the company's own team page. It also runs a departure check on the name by itself, which is what catches a name change.

When none of that confirms the role, Legatus marks it as low confidence and notes when the title was last publicly confirmed. The strategy then puts verification as the first step rather than building an approach on a person who may have moved on.

The wider rule is the same one everywhere in the playbook now: a fact Legatus couldn't verify can't carry the argument. It won't anchor Why now, Why us or the first move on something unconfirmed, and where the research contradicts itself, it shows you the conflict instead of quietly picking a side.

Until now, a workspace had one login that everyone shared. That's changed. Every person on your team now has their own login, tied to their own email, inside your workspace.

Two ways in, both of them fast. Sign in with Google and you're one click from your accounts. Prefer email? Enter your address and we send you a link that logs you straight in.

Invite a colleague by email, they click the link, and they land in your workspace as themselves. No password to pick, no password to forget, nothing to reset.

A timing signal is only useful if there is still time to use it. An account can be in the middle of something big, but if the moment crests before your first email lands, it was never an opening.

Legatus now weighs the runway on every timing signal it finds. When it builds the “Why now” section of a playbook, it anchors on events that are live and still have room to act, not events that will have passed by the time you reach out.

Take two signals.

"They're running a big World Cup activation" is happening right now, and right now feels like the perfect moment. But when the final whistle blows, the campaign comes down and the moment goes with it.

"They opened a new production site this spring" sounds like old news, but the ramp-up behind it runs into next year. Live is not the same as open. Legatus now judges how much road is left, not how recent the event is.

The result: when a playbook says now, you can trust that now still means something by the time you pick up the phone.