01 / Studio boardHours on the left, launches on the right.
Each retainer is a tank filled to the hours logged this month, with a mark at the pro-rata point for today. Each build is a runway row with its days to launch and its checklist counts.
GoSeedly Web & Software Agency Kit
Every retainer hour
accounted for.
A retainer hours tank wall beside a launch runway. Sprintline puts the hours a client bought, the hours your team logged, and the checklist a build has to clear before it goes live on one screen.
Checking access…See the interface
One-time purchase · USD · Your Seedly backend · Editable kit sourceYOUR SPRINTLINE STUDIO BOARD
01 — STUDIO BOARDActual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
Built around the two things that cost a studio money.
One connected workspace, with views built around the decisions your team makes each day.
01 / Studio board
02 / ClientsOne line per client engagement.
A retainer sells a block of hours a month. A fixed-scope build is sold for a fee and ends in a launch. The same client can hold one of each as two records.
03 / RetainersHours against the block.
Hours used, the pro-rata point for today, overage recorded as hours, rollover carried in and the renewal date, with the month’s hours rows by date and person underneath.
04 / ProjectsBuilds by the stage the work reached.
Discovery, design, build, QA, launch and warranty, with days in the current stage, the fixed fee and every change request recorded against it.
05 / Launch checklistsEverything still open or blocking.
Every item that is not marked done, soonest launch first, grouped by content, design sign-off, QA, accessibility pass, redirects, analytics, DNS and SSL, backups and training.
06 / Support and care plansThe sites you look after.
Renewal month, the days until it, and the date of the last update run somebody recorded. The kit runs no update and checks no uptime.
07 / InsightsWhat the studio wrote down.
Recorded hours against the agreed blocks, hours past them, checklist counts and renewals due, with the engagements behind each figure.
YOUR PROCESS, YOUR STARTING POINT
Useful structure.
Only what you choose.
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
Choose your starting structure.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
- Retainers · 7 stages
- Fixed-scope builds · 8 stages
- New business · 7 stages
- Care plans · 7 stages
Give the next step a shape.
- New enquiry task
- Discovery call note
- Proposal follow-up after a wait
- Kickoff task
- Monthly retainer summary task
- Over-hours conversation task
- Launch minus seven days check task
- Post-launch warranty end reminder task
- Care plan renewal task
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
Explore before adding records.
Explore 16 fictional engagements: nine retainers, seven fixed-scope builds across all six stages and five care plans. 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.
Three ready-to-edit forms.
- Project enquiry
- Support request
- Launch sign-off request
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Three reusable templates.
- Retainer monthly summary
- Launch checklist sheet
- Change request note
Open each template in Documents and complete it for the actual job or visit.
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 engagement holds the client label, whether it is a retainer or a build, the monthly block of hours, the hours rows staff logged with a date and a person, rollover and renewal, a fixed fee and its change request rows, the stage and its date, a launch date, the launch checklist and care plan details.
Studio board with the retainer hours tank wall and the launch runway
Clients operating view
Retainers operating view
Projects operating view
Launch checklists operating view
Support and care plans operating view
Insights operating view
Three native form drafts and three editable document templates
Editable per-engagement checklists and preserved row history
Four optional pipeline templates and nine inactive workflow drafts
16 fictional in-memory engagements
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Read the installation guide FROM KIT TO CONNECTED WORKSPACE
Check. Connect.
Make it yours.
Check your Seedly project.
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
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.
Set up your own team.
Edit business 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 engagement creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, check revisions before saving, and run the same credential guard the browser runs. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Hours are stored as whole numbers of hundredths of an hour, so 2.5 and 2.75 are exact and nothing is rounded before it is added up. The pro-rata point, rollover, days to launch and the renewal windows are all calculated from recorded rows. The kit stores no password, API key, token or hosting login and refuses the obvious accidental entries in every free-text field, which is a guard against accidental entry rather than a guarantee. It is not a time tracker or a timesheet, it connects to no repository, issue tracker, host, DNS provider or uptime monitor, it deploys nothing, it invoices nobody, and an accessibility pass recorded here is a check a member of staff made rather than an audit.
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.
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.
See DevLaunch All AccessAlready a member? Open your downloads.
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?+
Sprintline keeps its ink rail and white canvas across the kit 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.
Find a workspace that fits the way you work.
Explore all CRM kits