Clients, projects and the money โ in one place, in your language.
Kadima Ltd โ the org chart
Run 84391 ยท Call centre handoff
One record moves through all three. The offer becomes the project, the project's runs become the invoice, and the invoice's payment reopens the loop โ no re-keying, and no second system to reconcile against.
An accepted offer provisions the project, its team and its billing. Tasks land on one board for people and agents.
A workflow is a versioned document of stages. Any stage can be a person, an agent, a team, a platform action or an integration; routing is typed rules with a required default, so every transition records why it happened rather than only that it did.
A person's day is what only a person can do: approve, sign, decide, talk to the client. Drafting, triage, reconciliation, scheduling, testing and reporting run beside them on the same boards โ and every result arrives as a proposal, never as an overwrite.
Offload โ An agent's ceiling decides what never reaches you. Everything under it completes and is recorded; nothing under it interrupts.
Alongside โ The same board, the same thread, the same task list for people and agents. There is no second system for the machine half of the team.
Confirm โ Anything that leaves the company waits for a person โ a signature, a payment, a merge, a message to a client.
Seniority is a permission ceiling, not a label. A junior proposes; a senior may accept a junior's work inside a defined scope; a lead is a person, and only a person confirms anything that leaves the company. Agents earn the next rung from their record.
An agent that proposes. It drafts, triages, reconciles and tests; everything it writes is marked with its origin, and it cannot accept its own work.
An agent that approves inside a scope a person defined โ a price band, a test suite, a message template. What falls outside it escalates.
A person. They own the team's standing grants and ceilings, and anything that leaves the company is theirs to confirm.
One configurable platform underneath, not a shelf of products. A record type you define on Monday has a list, a form, a board and a detail page on Monday. Workflows, agents, skills, routines and integrations are versioned documents, so a change is a new version and never touches work in flight.
Define a record type on Monday and it has a list, a form, a board and a detail page on Monday. The nouns are yours; the platform underneath is one.
A workflow is a sequence or a graph, with rework loops allowed. A change is a new version, so work already in flight keeps the version it started on.
An agent's model is a setting with a primary and fallbacks, not a property of the platform. Design agents can run on one provider, coding agents on another, and patient data on a model you host yourself. Swap a provider in one place; no workflow changes.
| Agent |
|---|
Noa Levi10:44
Find 30 minutes with Amit this week to walk through the Kadima phase 2 offer.
Noa's agent10:44
Asking Amit's agent for his availability. I will only book inside your working hours.
Amit's agent10:46
Amit is free Wednesday 14:00โ15:00 and Thursday 09:30โ11:00. He prefers Thursday for offer reviews.
Who asked, which agent answered, under whose grant, what it touched and what a person did with it. Filter by agent, by person, by outcome. Set a ceiling and the agent cannot exceed it; revoke a grant and it stops.
| Time | Person |
|---|
A plugin brings a capability, its team and its billing together. Install one on a company or on a project, and the definitions, workflows, agents and routines it needs arrive with it.
Build
Sales
Finance
People
Marketing
Handled since 07:00
Code lives in the platform's own Git. Agents open pull requests that carry their run id; the merge stays a human act.
Clients follow the project, watch spend at their own price, and pay invoices whose every line traces to what caused it.
Offer accepted
Draft the packet
Review the draft
Revise
Countersign
Issue the invoice
Inbound call
Answer and identify
Within my ceiling?
Resolve
Take the call
Close the case
Push to branch
Run CI
Write and run tests
Review the diff
Merge
Watch logs ยท 60 min
Application submitted
Verify KYC / KYB
Assemble the file
Credit decision
Draft the letter
Record the outcome
Booking created
Consent via WhatsApp
Intake questions
Summarize for the clinician
Confirm the file
Visit ready
1st of month ยท 06:00
Pull the bank feed
Reconcile
Draft reminders
Render the report
Approve and send
Brief approved
Draft 7 posts
Build the ad set
Approve posts and budget
Publish ยท Meta
Launch ยท Google Ads
Purchase events on signed offers
Case opened
Trace the failing runs
Reproduce
Draft the reply
Approve and send
Reply on WhatsApp
Seat created
Prepare the checklist
Mailbox and calendar
Grant access
Schedule the 30-day review
Seat active
Lead โ qualified โ offer
Case triage and reply
Offer signed โ ad conversion
Weekly social calendar
Onboard a new seat
Monday project report
What people changed
Alert โ case โ owner
Invoice โ reminder โ paid
| Time | What happened | Reached Noa? |
|---|---|---|
| 07:10 | 12 leads triaged and scored | no ยท inside the ceiling |
| 08:02 | Offer OFR-0451 drafted and priced | no ยท went to a senior |
| 08:40 | Offer OFR-0451 approved by quote-review โ awaits Noa | yes ยท decision |
| 09:15 | 4 follow-up emails drafted | no ยท inside the ceiling |
| 10:48 | Meeting booked with Amit's agent | no ยท inside the ceiling |
| 11:30 | Call escalated โ a client wants to cancel | yes ยท escalation |
| Agent ยท skill | Evidence | Change |
|---|---|---|
| offer-drafts ยท pricing | 212 accepted unchanged | junior โ senior |
| qa-tests ยท test authoring | 0 escaped defects ยท 90 days | skill offered to the team |
| collections ยท Hebrew register | 48 sent as drafted | scope widened |
| pr-review ยท review comments | 31% changed by people | stays junior |
A seat is not a grant. Adding an agent to a team gives it a place to stand; what it may do is a separate act a person performs.
A skill is a versioned bundle of instructions and tools. Any seat can bind one, and one that keeps producing accepted work is offered to the whole team.
A routine is a schedule with a timezone that starts a workflow. It runs under a standing grant, and it stops the moment that grant is revoked.
The client portal resolves the client's brand before first paint โ their logo, their colours, their language, mirrored rather than translated.
| Task |
|---|
| Model |
|---|
| Provider |
|---|
| ui-drafts | Screens and copy for the client portal | gpt-5 | OpenAI |
| pr-review | Diff review, test authoring | claude-sonnet-4-6 | Anthropic |
| call-agent | Voice, Hebrew, low latency | gemini-2.5-flash | |
| intake-drafts | Patient intake summaries | gpt-oss-120b | self-hosted |
| collections | Reminder drafts, with a fallback chain | mistral-large โ haiku | Mistral |
Noa's agent10:46
Booked Thursday 09:30โ10:00, โKadima phase 2 โ offer walkthroughโ, with the draft attached. Reminder set for 09:15.
Every signed-in person has a personal agent that can do anything they can do, and nothing they cannot. It reads your calendar, drafts your replies, books with a colleague's agent or a client's, and reminds you what is due. Each side acts under its own principal, and both runs are on the record.
| Agent ยท what |
|---|
| Grant |
|---|
| Outcome |
|---|
| 09:41 | Noa Levi | offer-drafts ยท drafted OFR-0451 | standing ยท Noa | accepted |
| 10:46 | Amit Cohen | Amit's agent ยท shared availability | personal ยท Amit | completed |
| 11:30 | Yael Shapira | call-agent ยท handed off a cancellation call | standing ยท Yael | escalated |
| 12:05 | Roni Bar | collections ยท 4 reminders drafted | standing ยท Roni | 1 edited |
| 13:12 | Amit Cohen | pr-review ยท 3 comments on PR #418 | standing ยท Amit | 2 kept |
| 13:40 | Dana Peretz | ads-events ยท uploaded conversion events | standing ยท Dana | approved |
| 14:02 | Roni Bar | billing-runs ยท reconciled the month run | standing ยท Roni | 1 confirmed |
| 14:15 | Noa Levi | offer-drafts ยท revised the price band | standing ยท Noa | accepted |
Startups run the whole company here from day one. Existing companies start with one department and move the rest when they are ready.
Five founders, a full org chart. Sales, delivery, support and finance staffed by agents that report to you.
Repos, CI/CD, QA and log monitoring as workflows. Agents open pull requests; people merge.
Campaigns, social calendars, Meta and Google Ads events, drafts and reporting on a routine. Every post and budget change approved by a person.
Boards people and agents share. Status, risks and the weekly report written from the record, not from memory.
An industry solution is a versioned bundle of definitions, workflows, agents and documents, in your field's own nouns.
Applications, applicants and decisions as records; KYB/KYC before anything; a person on every credit decision.
Patients, referrers and visits; consent before booking; intake and summaries on a model you host, in Hebrew.
An integration exposes typed operations with a policy matrix and quotas. Workflows use them as nodes; nothing else can call them.
Identity and business verification as a gated node, with the response kinds your routing can read.
Messages, templates and media with per-day quotas โ the consent channel for medical, the reminder channel for loans.
The platform's own Git plus GitHub. Pull requests carry the run id that produced them.
Inbound and outbound calls as runs, recordings as facts, handoff to a person mid-call.
One agent concept: a seat on a team with a seniority ceiling, a model setting and bound skills. It proposes; a person confirms.
Answers, identifies, resolves inside its ceiling and escalates with the transcript attached.
Writes tests from the diff and the spec, runs them, and reports what failed and why.
Reads a pull request and proposes comments. A merge is always a person's act.
Drafts reminders for overdue invoices in the register you choose. Sends nothing itself.
A skill is a versioned bundle of instructions and tools. Any seat can bind one โ an agent or a person. A skill that keeps producing accepted work is offered to the whole team.
Formal Hebrew for offers, invoices, clinical and financial copy.
Matches payments to lines; flags what does not reconcile; never writes a confirmed figure.
When to hand off: money, cancellation, distress, or anything outside the ceiling.
From a diff and a spec to a test plan and runnable tests in your stack.
A routine is a schedule with a timezone that starts a workflow. It runs under a standing grant a person gave, and stops when that grant is revoked.
Reads the day's logs, groups errors, opens a case when a rate moves.
Status, risks and spend per project from the record, drafted for the project lead.
Reconcile, chase, report โ approved by the controller before anything is sent.
Drafts the week's posts from the campaign brief for a person to approve.
A plugin is how any of this is sold and metered: install one on a company or a project and the capability, its team and its billing arrive together.
Pipelines, environments and releases as workflows on the platform's Git.
Ingest, group, alert, open a case. A person owns every alert that matters.
Campaign briefs to scheduled, approved posts, ad conversion events to Meta and Google, and a weekly report.
Inbound and outbound calls with handoff and escalation to a person built in.
A mailbox per person, team and company; calendars your agent can book against.
Server-side conversion events from signed offers and paid invoices, matched to the click that brought the lead. Budgets change only with a person's approval.
Invoices paid in the client portal; the bank feed reconciled by an agent, verified by a person.
Sends purchase and lead events to Meta and Google Ads from what actually happened โ a signed offer, a paid invoice โ and proposes budget shifts.
Turns the campaign brief into a month of drafts on the calendar, for a person to approve.
Reads a case, traces it to the runs that failed, proposes a cause and an owner.
Assembles a decision file against your credit policy, with every source cited.
Compares what agents proposed with what people changed, and proposes skill edits.
Calendar, drafts, approvals and replies across channels.
Reconciliation, collections, month-end close and the reports.
Cases, triage, proposed causes and a client-visible thread.
Leads to signed offers, with a drafting agent and a quote reviewer.
Weekly and monthly reports written from the record for every project and department.
What people changed becomes what agents learn โ and what promotes them.
Seats, onboarding, leave and reviews for people and agents on the same chart.
Tests authored from the diff, run in CI, reported to the merge gate.