GoSeedly Virtual Assistant Agency Kit
An hours board for virtual assistant agencies: every client down the side, every assistant across the top, and in each cell the hours that assistant recorded inside the client's current plan period, next to the plan hours. Deskhand keeps the time log, delegated tasks, assistant coverage, plan periods and the client roster in one connected workspace, and it keeps client logins out of the CRM.
YOUR DESKHAND WORKSPACE
01 — HOURS BOARD
Actual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
One connected workspace, with views built around the decisions your team makes each day.
01 / Hours boardA needs-attention strip, then one row per working client and one column per assistant, each cell the hours recorded in the client's current plan period with Primary or Backup written out. Recorded hours sit against plan hours with the hours left or over in words. Clients over the plan, at 90% of it, with no plan period today, with a period ending and no next one, with no assistant today or with a late task lead.
02 / Time logThe last 14 days of time entries, newest day first, each day with its recorded hours and every entry: the assistant, the client, the task label as typed and the hours.
03 / TasksTasks past their due date first, then open and waiting-on-client tasks by due date with how often each repeats, then the tasks done in the last 30 days.
04 / AssistantsOne card per assistant with the clients they cover today as primary or backup, their recorded hours for the last 7 and 30 days, and their open delegated tasks on a separate line. Clients with no assistant today are listed underneath.
05 / PlansCurrent plan periods with plan hours, recorded hours and the hours left or over, the next period or a flag when none is recorded, clients working without a plan period, upcoming periods, and recorded plan fees in a ledger of their own.
06 / Client rosterOpen clients from inquiry to active with the account lead, start date, primary assistant today, how access is shared and the current period, then clients paused or ended in the last 30 days.
07 / InsightsClients by stage and kind, recorded hours by assistant, delegated tasks by status, assignments by role and recorded plan fees by client kind. Hours, tasks and dollars are never added together or drawn on one scale, and no ledger scores an assistant.
YOUR PROCESS, YOUR STARTING POINT
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
Explore 12 fictional clients and four assistants: ten open (one inquiry, one onboarding and eight active), one paused and one ended, with 20 plan periods, 14 assignments, 53 time entries, 18 delegated tasks and 84 checklist steps. Sample edits stay in memory and reset on navigation or reload.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
Editable native forms and document templates give your team a practical starting point.
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Open each template in Documents and complete it for the actual job or visit.
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
One contact-linked client holds the client kind, the account lead, how access is shared, the inquiry, start, pause and end dates, plus every plan period with its plan hours and recorded fee, every assignment with its role and dates, every time entry with its assistant, hours and task label, every delegated task with its due date and status, and an editable checklist.
FROM KIT TO CONNECTED WORKSPACE
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
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.
Edit business name, descriptor and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
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 creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, keep every task label exactly as typed, refuse passwords, logins, 2FA codes, API keys, card and bank numbers and Social Security numbers, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Deskhand records the plan hours the office agreed and the hours the assistants recorded, and compares them only with each other. It makes no productivity, turnaround or results promise and no statement about whether an assistant is an employee or a contractor. It does not track time, approve timesheets, run payroll, invoice, take payments, send messages or collect signatures. Client credentials belong in the client's password manager, never in the CRM: passwords, logins, 2FA and backup codes, API keys and tokens, payment card numbers, bank account and routing numbers, Social Security numbers and door codes are refused in recorded text and in the native form drafts.
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
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.
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
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
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.
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.
Deskhand keeps its wine-stone top bar and wine pill tabs across the kit views and 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.
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.
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.
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.
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 kitsCustomer experiences / Trustpilot
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
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.
Read our Cookie Policy and Privacy Policy.