Home · Matrix · Funds and Advisory Firms · Outbound engine · vs Swan
vs Swan
Midsummer vs Swan for funds outbound engine.
Two ways to run outbound engine for funds and advisory firms. The difference is who approves, and what you can read afterwards.
Midsummer vs Swan for funds outbound engine: Swan turns a written prompt into a workflow. Midsummer is a department that takes the outcome and owns it. With Midsummer, every external message waits as a draft until a person on your team approves it, and every action is logged with its source.
The difference
Swan turns a written prompt into a workflow. Midsummer is a department that takes the outcome and owns it.
Midsummer and Swan
| Midsummer | The other side, from its own site | |
|---|---|---|
| Does a person approve before it sends? | Yes, always. Every send waits for a person on your team. | Review appears in their workflow examples. Their page does not state that approval is required. |
| Who makes the decisions? | Your team, at every irreversible step. | Their page says the product weighs context, evaluates options, and decides on its own. |
Source: getswan.com home page, captured 2026-09-06.
The working law
Whatever the page, the working law does not change: every external message waits as a draft until a person approves it, and every action is logged with its source so you can open it and check. Approval is not a mode you turn on; it is how the department works.
Common questions
Does Midsummer send without approval?
No. Every external message waits as a draft until a person on your team approves it. That is the working law, not a setting.
What can we read afterwards?
Everything. Open any action and read what ran, what it said, and what came back, with the source attached.
What does it need to start?
Read access to your CRM and inbox, scoped in writing at onboarding. Revoke it and the work stops.