A console for agencies and freelancers who sell AI and workflow automation: process audits, n8n, Make, Zapier, custom code, CRM workflows, AI agents and chat or voice assistants, then monthly care plans. Loopwork puts every automation you delivered on one board, flags the ones that need attention and ships with 31 workflow drafts for the work around them.
Lanes run from discovery to scoped, building, client testing and live. A live automation moves into Needs attention, in words and with a notched card, when its last recorded health check is older than the window you recorded, no check is recorded or a break-fix request is open. Retired automations are counted, never drawn as cards.
Inquiry, discovery call, audit booked, audit delivered, proposal, won and lost, with the recorded audit fee, proposal value and stage date on each client, and proposal values totalled per column.
Each process with its recorded manual hours per week, the estimated hours an automation would save, effort and priority. Totals stay in hours per week; prices live in the proposal.
A numbered stepper per automation: scope signed on paper as recorded, access requested, credentials handed over through the client’s password manager, spec approved, build, test cases, client UAT, handoff doc, training and live. Every step is editable.
Plan tier, recorded monthly fee, care hours used against hours included, days to renewal and the next quarterly review. A client past its included hours is flagged.
Change requests and break-fix requests with the received date, the response the team recorded and the state. An open break-fix leads the list and flags its automation on the board.
Monthly recurring revenue from recorded care fees, recorded hours saved by client, win rate and build cycle time, each in a separate ledger with the same flags as the board.
YOUR PROCESS, YOUR STARTING POINT
Useful structure. Only what you choose.
4 pipelines and 31 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
01 / FOUR PIPELINES
Choose your starting structure.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
New business · 8 stages
Build delivery · 8 stages
Care plan · 7 stages
Expansion · 6 stages
02 / 31 WORKFLOW DRAFTS
Give the next step a shape.
Lead and audit · New inquiry triage
Lead and audit · Discovery call prep
Lead and audit · Discovery no-show follow-up
Lead and audit · Audit booked prep checklist
Lead and audit · Audit delivered, proposal due
Lead and audit · Audit not converted, 30-day nudge
Proposal and close · Proposal follow-up cadence
Proposal and close · Proposal viewed but stalled
Proposal and close · Won, schedule kickoff
Proposal and close · Lost, reason note and 90-day revisit
Onboarding and access · Kickoff scheduling
Onboarding and access · Access request checklist
Onboarding and access · Credential handover reminder
Onboarding and access · Tool accounts confirmed
Onboarding and access · Onboarding stalled
Build and QA · Build started
Build and QA · Spec approval chase
Build and QA · Internal test pass
Build and QA · Client UAT reminder
Build and QA · UAT stalled escalation
Launch and handoff · Go-live checklist
Launch and handoff · Handoff doc and training
Launch and handoff · 7-day post-launch check
Care and retainer · Monthly health check tasks
Care and retainer · Break-fix request intake
Care and retainer · Care hours at 80 percent
Care and retainer · Quarterly review prep
Care and retainer · Care plan renewal, 30 days out
Growth · Case study request after 30 days live
Growth · Referral ask after a positive review
Growth · Expansion from the audit backlog
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
03 / SAMPLE WORKSPACE
Explore before adding records.
Explore 10 fictional client accounts with 20 automations (8 live, 3 needing attention, 2 retired), 22 audit processes, 70 build steps across seven checklists and 8 requests. Sample edits stay in memory and reset on navigation or reload.
No sample customers are inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
From the first inquiry to the final handoff.
Editable native forms and document templates give your team a practical starting point.
01 / INTAKE & FOLLOW-UP
Three ready-to-edit forms.
Automation audit request
Break-fix or change request
Care plan inquiry
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
02 / WORKING DOCUMENTS
Three reusable templates.
Process audit summary
Automation build proposal
Handoff and care plan summary
Open each template in Documents and complete it for the actual job or visit.
03 / THE NEXT STEP
Checklists alongside the work.
Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.
Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.
THE KIT, UNPACKED
Your workspace. Your starting point. Your code to edit.
One contact-linked client account holds the new-business stage and dates, the recorded audit fee and proposal value, the care plan tier, fee, hours included and used, the health check window and renewal and review dates, plus four child lists: automations, audit processes, build steps and change or break-fix requests.
Automation inventory board with client swimlanes and a Needs attention lane
New business, Audits, Builds, Care plans, Requests and Insights views
31 inactive workflow drafts in seven groups, from inquiry triage to care plan renewal
Three native form drafts and three editable document templates
Standard ten-step build checklist per automation, fully editable
Server-enforced credential guard on every free-text field
Four optional pipeline templates and 31 inactive workflow drafts
10 fictional in-memory client accounts with 20 automations
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
02
Connect the required helper.
Deploy the included helper from your authoritative backend source before connected edits. Build your web app, then choose any optional pipelines and drafts you need.
03
Set up your own team.
Edit agency name, descriptor and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
Compatibility and operational details
Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original backend helpers are required for connected client records, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, check revisions before saving and refuse credentials on the server. Deploy them from the authoritative backend source. Pipelines and all 31 workflow drafts are optional and install inactive.
Loopwork records what your team agreed and did. It does not run, host, monitor or connect to any automation platform: no uptime monitoring, no API integration with n8n, Make or Zapier, no time tracking or invoicing, no AI features inside the kit and no automated messaging. Hours saved are recorded estimates, not measurements, and hours are never added to money. Credentials never live in the CRM: API keys, tokens, passwords, webhook URLs that carry a secret, private keys, card numbers and SSNs are refused in every free-text field, on the server as well as in the browser. That is a guard against accidental entry, not a guarantee.
Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.
Checking access…
DEVLAUNCH ALL ACCESS
Every kit. And everything else.
DevLaunch All Access includes every GoSeedly CRM kit, all 195 available today, along with every class, course, and product we release, and private calls with Aaron.
All 195 CRM kits
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
Every class, course, and product
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Private calls with Aaron
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
DevLaunch All Access
Want more than one kit? All Access covers the whole CRM kit library and the rest of what we make. See everything it includes on the All Access page.
For your own compatible Seedly CRM. Seedly software, hosting and installation services are separate. Each full-interface kit uses its own web installation.
BEFORE YOU MAKE IT YOURS
Good questions. Clear answers.
How do I receive the kit?+
Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.
Does this include Seedly CRM?+
You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.
Is this one connected workspace?+
Loopwork keeps a dark console rail beside a light work canvas across its seven views and the native CRM tools in the same signed-in account. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.
Can I use it with existing customizations?+
Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.
Do I have to import all the starter content?+
No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.
Can I remove the examples and starter content?+
Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.
Can different subaccounts use different kits?+
The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
Your privacy, your choice.
We use essential storage to keep the site working. With your permission, we also use analytics and the Whop Pixel to understand visits and advertising results. Optional analytics stay off until you choose.