CRM KitsIT services & MSPs
Every ticket, every renewal, one console.
An MSP does not work a funnel. It works a queue. Uptime is a full dark console where the client rail, the ticket queue and the selected ticket stay on screen together, so choosing a client never costs the queue.
Three panes, one question at a time.
The rail lists every client contract with its open ticket count, days to the recorded contract end and a health dot. The middle pane is that client’s queue. The right pane is the selected ticket’s recorded notes, status and target, above a compact contract summary. Each pane scrolls on its own.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Three-pane console with a client rail, the selected client’s ticket queue and a ticket detail pane, each with its own scroll region
- Advisory response-target marking on unresolved tickets, stated as advisory everywhere it appears
- Ticket queue across all clients with recorded status and priority filters
- Clients table with the native CRM stage control, onboarding checklist cards and 30, 60 and 90 day renewal bands
- Insights over recorded statuses, priorities, resolution share and monthly reference totals by currency
- Installation-wide dark navy theme, so native CRM pages render as dark surfaces in the same frame, with full CRM tools
four pipelines
- Ticket handling · 8 stages
- Client onboarding · 7 stages
- Contract renewal · 7 stages
- Project work · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Ticket triage
- Response target check
- Resolution confirmation
- Onboarding kickoff checklist
- Network assessment
- 90-day renewal review
- 30-day renewal confirmation
- Project scoping
- Quarterly business review
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore eight fictional client contracts carrying 24 recorded tickets and five onboarding checklists, including two tickets whose recorded response targets have already passed. Example edits stay in the current page’s memory and reset on navigation or reload; sample clients are never inserted into your CRM.
No sample customers are added to your CRM.
Setup and source
- Guided setup and compatibility report
- Private rollback receipt
- AI-agent guide for customized installations
- Original editable source, configuration, and tests
How setup works
Full installation guideCheck your Seedly
Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.
Connect the helper
Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.
Make it yours
Set company name, descriptor, and default pipeline name. Then sign in and check the workflows and permissions your team uses.
Technical details and compatibility
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 MSP helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, keeps stable ticket and checklist IDs, and checks the current record state before saving. Stage changes use the host’s own pipeline mutation, so they obey your existing roles. Deploy the helper from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
A client contract is a native contact-linked opportunity with a namespaced client label, contract type, seat count, monthly reference, contract start and end dates, technician label, response target label, a recorded next step, ticket rows and onboarding checklist rows. The monthly reference stays separate from native opportunity value. Other custom fields are preserved, and both child collections are archived rather than dropped from a save.
This is not a PSA and not an RMM. Nothing is monitored, scanned, discovered, patched or inventoried, and nothing is read from or written back to a monitoring platform. There is no email-to-ticket intake, no notifications, no messaging, no remote access and no client-system scripting. A ticket row exists because a person typed it. The response target is a recorded label on the contract and a recorded hour count on the ticket; the console compares that count against the recorded opened time in the browser and marks an unresolved row red when it has already passed. Nothing pauses, escalates, breaches, credits or reports on a service level. Renewal bands read recorded contract end dates and nothing more. There is no billing, invoicing, contract signature, documentation store or credential vault. The recorded resolution share is resolved divided by resolved plus open plus pending, and returns unavailable rather than a zero when no ticket qualifies.
Four optional pipeline templates and nine inactive workflow drafts. Eight fictional in-memory client contracts with 24 recorded tickets and five onboarding checklists.
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.
Get the IT Services & MSP Kit
Checking access…
DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 270 website templates for Seedly Sites
- Every class, course, and product we release, added as it ships
- Private calls with Aaron
Already a member? Open your downloads.
Questions
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?
Uptime keeps its MSP navigation across the original console views and native CRM modules. Full CRM tools remain available within the same signed-in account and application theme. 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.
More professional services kits
Browse all 220 kits
