Every module gains an AI surface. Same record, no parallel system.
AI on every Operation. / MCP into every workflow.
WorkLet runs on a structured record, so AI has clean inputs by design. Operations draft themselves. Datarooms index themselves. Scenarios flex on a single prompt. And the same record opens to your tools through Model Context Protocol, so Claude, Cursor, and your internal copilots operate on WorkLet without leaving the surface your team works in.
Six Operations. One AI surface.
WorkLet AI lives where the Operations already live. It drafts, screens, scores, and reconciles. The operator stays in the loop, and every action is attributed.
Property Data
Drop a PDF teaser, an Excel rent roll, or a photo of a facade. The record fills itself with the fifty plus structured fields. The operator confirms.
DRAFTSDataroom
Auto index the documents the prospect will expect. Generate a per recipient briefing note. Surface gaps before the buyer surfaces them.
INDEXESSales & Acquisition
Score incoming offers against the mandate. Draft a counter on the property record. Summarise the day in the pipeline.
SCREENSCRM
Match the property to the right buyer in the CRM. Draft the briefing email. Flag relationships that went quiet and propose the re warm.
MATCHESManagement
Read the maintenance ticket, suggest the vendor from history, schedule the visit. Reconcile service charges against the leases automatically.
RECONCILESInvestment Analysis
"Flex exit cap by 25 bps." The model re prices the scenario in seconds, side by side with the base case, in your home currency and the buyer's.
FLEXESBring your own copilot. Operate on WorkLet.
WorkLet exposes an MCP server. The AI tools your team already uses can read the record, brief the dataroom, and execute Operations. The operator keeps the final keystroke; the platform keeps the audit trail.
Read the record
Every property, customer, deal, and dataroom file is callable as a tool. The same structured schema your team reads.
Trigger Operations
Draft a record, brief a dataroom, generate a counter offer, schedule maintenance. Twenty four tools at launch.
Scoped, audited, revocable
Per user, per tool, per Operation. Every call timestamped. Revoke access in one move.
Model agnostic
Plug in any MCP capable client. We don't ship a model. We ship the surface your model operates on.
Claude
In the team's chat or the IDE.
Cursor
For the analyst at the model.
Internal copilot
Your stack, your model, your prompt.
workletmcp.io
DE hosted. BDSG / DSGVO. Scoped tokens. Audit log.
Property Data
The structured record. The single source.
Dataroom · CRM · Sales · Mgmt · Analysis
Every module callable as a tool.
A morning on WorkLet with AI.
Two short workflows. The operator runs the day from the AI surface. WorkLet does the keystrokes.
From a PDF teaser to a briefed dataroom.
Read this teaser. Create the property record, then brief the dataroom to the two Tier A prospects.
Property created. Stiftsplatz 12. Mixed use. Asking 14.4 M. Fifty two fields populated. Two gaps flagged: WALT and EPC.
→ property.draftBriefing prepared. 14 documents, watermarked, 21 day expiry. Awaiting confirm before send.
→ dataroom.briefSend.
Flex three scenarios. Pick one. Brief the IC.
For Stiftsplatz 12, flex exit cap by plus 25 bps and minus 25 bps. Hold base. Report IRR and EM, side by side, in EUR and CHF.
Base 9.4%. Stretch 12.1%. Stress 6.7%. EM 1.51 to 1.96. CHF mirror prepared.
→ scenario.flexLock Stretch. Compile the IC pack.
Scenario locked. IC pack exported as PDF, attached to the record. Same numbers, both currencies. No reconciliation step.
→ deal.advanceAI you can put in front of a CFO.
The same posture as the platform. Operated under audit, hosted in Germany, scoped per user.
Hosted in Germany
Inference and storage stay in DE. No data leaves the jurisdiction unless you choose to send it.
Scoped per user
Every MCP token is bound to a user, a role, and a list of tools. Revoke in one move.
Audit trail
Every AI call, every tool invocation, every record edit. Time stamped, attributed, exportable.
Operator in the loop
AI drafts. The operator confirms. Sensitive Operations require a second key by default.
Bring your copilot to the property record.
Tell us which AI surface your team operates from. We brief the MCP integration, scope the tokens, and walk through the audit posture.