ASTRA / How it works
How ASTRA works
ASTRA runs a fixed five-step loop on every workflow: capture the commitments from the call, draft the action each one implies, hold the consequential ones for human approval, execute inside your own accounts, then verify the write landed and attach a reversible receipt.
The loop is deliberately boring and always the same. A predictable shape is what makes an agent auditable: you can point at any action that ran last month and say which step produced it and who let it through.
Step one: what does capture actually read?
The transcript, and specifically the commitments inside it. Not a summary of the call, not sentiment, not a talk-time ratio. The output of this step is a list of things somebody promised, decided, or now owes: send the security report, file the bug, move the close date, loop in the solutions engineer.
Call sources are the ones your team already records in, Zoom and Gong among them. Nothing about capture requires a new recorder in the meeting.
Step two: how does a commitment become an action?
Each commitment is converted into something concrete in a specific tool. "We will get you the SOC 2 by end of week" becomes a drafted mail with the document attached and a task on the account. "Can you file that so we can track it" becomes a Jira ticket with the customer's own words in the description and a link back to the opportunity.
A drafted action is fully formed at this point. It has a target system, a payload, and a stated reason drawn from the moment in the call it came from. What it does not have yet is permission.
Step three: what gets held for approval?
Anything customer-facing and anything that writes to a system of record. Mail to a customer, a stage change on an opportunity, a renewal date, a ticket that a customer will see. Those wait for a person.
Reversible internal writes can run unattended, because the cost of getting one wrong is a click to undo rather than a conversation with a customer. Even those leave a receipt. The full reasoning is on the approval gate.
Step four: where does execution happen?
Inside your accounts, using credentials you granted, scoped to the objects you allowed. There is no Mindlyft database holding a shadow copy of your pipeline that later needs syncing. The opportunity that changes is the opportunity in your Salesforce org.
This is also why cancelling is not a migration. What was built keeps running because it was never running anywhere else.
Step five: what does verify prove?
That the write actually landed, not that the request was dispatched. Those are different claims and only one of them is worth anything. The step reads the target system back, confirms the new state, and records a receipt naming the action, the approver, the timestamp and the rollback path. See the audit trail.
What one request looks like in practice
A request is anything one engineer can ship inside your stack in roughly a week. You put it on a shared board, one is active at a time, and it ships by Friday. Iterations are unlimited, so "close but not quite" is a normal part of the week rather than a change order.
| Request | What ships |
|---|---|
| Post-call CRM | Opportunity fields, notes and next steps updated from the transcript, held for approval. |
| Sales to CS handoff | A structured handoff posted to the owning channel with the commitments attached. |
| CRM hygiene | Duplicate merges, required-field enforcement, owner routing, stale-opportunity sweeps. |
| Renewal risk | Signals from product usage and call language surfaced early, with the evidence attached. |
| Onboarding | The steps after signature turned into tracked actions instead of a checklist nobody opens. |
Out of scope on purpose: cold-email deliverability and domain warmup, contact scraping and list building, and strategy decks with no build attached. This is about finishing work a real conversation created, not manufacturing outbound volume.
Questions
How long does the first workflow take?
Requests are scoped to what one engineer can ship inside your stack in roughly a week, and shipping happens weekly. The first workflow is engineered end to end for free.
Does ASTRA need a new meeting recorder?
No. It reads transcripts from the call tools your team already uses, Zoom and Gong among them.
What counts as one request?
Anything one engineer can ship inside your GTM stack in roughly a week. Unlimited requests sit in the queue, one is active at a time.