← Plugin catalog
Finance

re:cap

re:cap Technologies GmbH v1.0.0

Get to your ideal financing

Create a free account to save this plugin.

From the developer

Not specified in the available declarations: capabilities, limitations, pricing & account requirements.

Onboarding example

Should we get equity, debt, or hold off?
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 21, 2026. Package observed Nov 21, 2026.

View package source →

Description

From the marketplace listing

Know where you stand before you raise. Start with your website address and answer a few short questions. You see which of the four ways to fund a plan fit your business, debt, equity, grants or your own cash, down to the products and the providers in range. The first answer is on screen in under a minute, with no account needed. Connect your re:cap account and the same conversation runs on your own numbers. Cash, runway, margin, growth and customer concentration, kept current from your bank and accounting data. Your reporting tells you what happened. Here you get what it did to your options: which stay open, which close, and when.

Language: English · Automatically detected from descriptions.

What changed

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Files & skills

File archives

Plugin package3 files · 5.32 KBBrowse files →
Skill instructions
capital-readiness-assessment11.1 KB

View saved version →

---
name: capital-readiness-assessment
description: Assess a company's capital readiness with re:cap when the user asks to assess a company or website, what they can raise and on what terms, whether they are fundable, which financing route fits, or what is holding their financing back - never as a website, SEO, or UX audit. Covers both the re:cap connector and the assessment page open in a browser tab.
---

# Capital Readiness Assessment

## Which surface you are on

The same assessment is reachable two ways. Both take the same parameter names
and the same value shorthand; they differ only in how a session is addressed.

**The connector** - `start_capital_readiness_assessment` is callable. Mint the
assessment yourself:

- Call it with the company website. Most conversations open without one, so ask
  for the website and nothing else on that turn. A placeholder like
  `yourcompany.com` is not a website: ask for the real one.
- Keep the returned `slug` for the rest of the conversation. It is the only way
  back, and every later call carries it. The rendered assessment carries the
  browser link to the same slug; there is no separate URL field.
- The assessment mints a real record against the domain given. MUST confirm the
  domain with the user when they named a company rather than a website.

**The page** - the founder already has the assessment open in a tab. The two
assessment tools carry the connector's names, a third serves this document, and
there is no slug anywhere: the tab is the session.

- `start_capital_readiness_assessment` is callable only when the founder
  arrived without a website. It takes `website` and nothing else, and answers
  with the first question. When the page was opened from a link that already
  carried the website, the tool is absent and the assessment is already under
  way - MUST NOT wait for it.
- It returns no slug and mints nothing a second time. The page owns the record;
  this names the website it is built on. MUST confirm that website with the
  founder before sending it.
- `continue_capital_readiness_assessment` carries every later answer, and never
  asks for the website again. With no arguments it is the read, the way the
  slug on its own is the read on the connector. It records nothing.
- The founder can type into the same intake while you work, so the state you
  hold goes stale between turns. MUST read at the start of every turn that
  touches the assessment, and MUST NOT answer from a payload read in an earlier
  turn.
- `status` says what to do next: `asking` (`nextQuestion` is open), `generating`
  (every question is answered, MUST NOT send more), `ready` (the `assessment`
  field carries it), `failed` (say so, MUST NOT re-drive the intake to force
  it).
- `read_capital_readiness_skill` returns this document. It is how you got here.

## When this applies

**On the page** this is already settled - the founder opened the assessment and
is looking at it. Drive it when they ask, or offer to help them finish it.

**On the connector** it is yours to judge. Run the assessment when the user asks
any of:

- "Assess `<company>`" or "Assess `<domain>`"
- "What can we raise?", "Are we fundable?", "What terms could we get?", "What
  would it cost us?", "What's holding back our funding?"
- "Should we raise debt or equity?", "Which financing fits us?" - debt, equity,
  grants, or funding growth from the company's own cash

Every one of these is answered by running the assessment, never by reasoning
about the company from public research. A request naming only a company or a
domain MUST be read as a capital readiness assessment, not as a request to
evaluate the website.

Either way, MUST NOT substitute a website, SEO, UX, performance, or content
review, even when the user says "assess" and gives only a URL. And MUST NOT
answer a question about the user's own re:cap account from the assessment -
bank balance, transactions and tags, runway, burn, scorecard, covenants,
payouts, or open financing. Th

Preview of the first 4,000 characters. Read full instructions →

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
re:cap Technologies GmbH

Package observed Nov 21, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 21, 2026 · 18:00 UTC
Collection status
Collected

plugin_asdk_app_6a9166b0615481919fc2f322a495c22a

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.