swift-saas
ship shopmake for me a boring saas idea from your head that solve boring problem
Comments (0)
Sign in to leave a comment
Run executions
Every occurrence of every configured workflow, newest first — the state it finished in, how long it took, and the onward connection for anything that needs a person.
| Run ID | Workflow | Started | Duration | State | Outcome | Follow-up |
|---|---|---|---|---|---|---|
| Run IDrun-8841 | WorkflowNightly invoice reconciliationwf-1042 | Started | Duration | StateIn progress | OutcomeStep 04 of 05 running | Follow-up Result must be re-checkedFollow up reviewed output |
| Run IDrun-8836 | WorkflowNightly invoice reconciliationwf-1042 | Started | Duration | StateFailed | OutcomeFailed at step 03 NotifyReached step 02 of 05 | Follow-up |
| Run IDrun-8829 | WorkflowWeekly vendor statement sweepwf-1057 | Started | Duration | StateAwaiting review | Outcome3 results awaiting review | Follow-up |
| Run IDrun-8822 | WorkflowNightly invoice reconciliationwf-1042 | Started | Duration | StateCompleted | OutcomeAll steps completed | Follow-up No follow-up required |
| Run IDrun-8815 | WorkflowMonthly access roster exportwf-1063 | Started | Duration | StateCompleted | OutcomeAll steps completed | Follow-up No follow-up required |
Nightly invoice reconciliation
- IMPORTImport ledger export — Completed00:12 recorded
- TRANSFORMNormalise line items — Completed00:21 recorded
- NOTIFYNotify approvers — Completed00:08 recorded
- REVIEWHold for reviewer check — In progress00:33 recorded
- ARCHIVEArchive reconciled batch — Pending—
The recurring chore that runs itself.
For operations staff at small and mid-sized businesses: configure a recurring workflow once, let it run on its cadence, and have the routine output reviewed before anyone relies on it.
Run timeline — recurring workflowRUN-0413
The routine runs on its cadence. Steps 01–03 and 05 completed without intervention; step 04 is waiting on the reviewer’s check.
A recurring workflow has one setup and two hands: someone describes the chore once, the system performs it on schedule, and a reviewer decides whether the result can be relied on.
- 01Configure once
The Operations Coordinator names the workflow, lays out its steps and sets the cadence — daily, weekly, or on the working days the team actually uses. This is the only time the chore is described by hand.
- Owner
- Operations Coordinator
- Configured
- Once, then saved
- 02Runs on its cadence
Once saved, the workflow executes on its own schedule without anyone starting it. Each occurrence produces a run record with its own run ID, and every step reports its state as it completes.
- Trigger
- Recurring cadence
- Output
- Run record per occurrence
- 03Review the output
The Team Reviewer checks the generated result for each run, confirms it as correct, or flags it as needing attention. A flagged item returns to the coordinator, who adjusts the workflow so the next occurrence runs cleanly.
- Owner
- Team Reviewer
- If flagged
- Returns to coordinator
04 — Who it is for
Built for the people who carry the recurring chore
swift-saas is for operations staff at small and mid-sized businesses — the two people who currently own a repeating back-office task and the check that follows it.
- Operations Coordinator 01
- The coordinator owns the recurring chore. They enroll themselves, name the workflow, choose the ordered steps and the cadence it runs on, and save it once so it becomes active. When a run fails or a result is flagged, the coordinator adjusts the workflow definition and lets the next occurrence run. Their work is configuration and follow-up — not checking the output by hand.Sets upCreates and changes the workflow definition, its ordered steps, and its cadenceActs onA flagged result arriving back from the reviewerSuccessThe workflow appears on Workflows with its cadence and runs on its own; the chore is no longer performed by hand
- Team Reviewer 02
- The reviewer is the second human in the loop and arrives through an invitation rather than enrolling. They check the generated results awaiting review on a recurring basis, seeing the run and the workflow each result belongs to, and then confirm it as correct or flag it as needing attention. Their confirmation is what makes the routine output trusted; their flag is what brings a problem back to the coordinator.ReceivesAn invitation from the coordinator, accepted to establish their own identityDecides per itemConfirm the generated result as correct, or flag it as needing attentionSuccessItems awaiting review are cleared, confirmed items carry a success state, and flagged items stay visible to the coordinator
No comments yet. Be the first!