01 / Intake gridSee every missing document at once.
One row per return engagement, grouped by recorded status. Each document column is filled when received, hollow while still requested and struck through when marked not applicable.
GoSeedly Tax Preparation Kit
Every document in.
Every return out.
A document intake grid for tax season. Ledgerday puts one row per return engagement, a document column set for that return type, a received-of-required count and a deadline countdown in front of the work that still needs a document.
Checking access…See the interface
One-time purchase · USD · Your Seedly backend · Editable kit sourceYOUR LEDGERDAY INTAKE GRID
01 — INTAKE GRIDActual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
Built around the documents that decide the week.
One connected workspace, with views built around the decisions your team makes each day.
01 / Intake grid
02 / ReturnsThe whole engagement ledger.
Review the client, tax year, return type, preparer label, status, received count and deadline for every engagement in the selected pipeline.
03 / Missing documentsChase the oldest request first.
Outstanding documents are grouped by client and ordered by the date they were requested, with the days each one has been outstanding.
04 / DeadlinesOne list, ordered by the date that counts.
Returns are ordered by the effective deadline. A recorded extension moves the date, and the countdown turns red inside fourteen days while documents are still outstanding.
05 / Review queueKeep the reviewer on the record.
Returns in preparation, in review or ready to sign, with their preparer and reviewer labels and a flag where no reviewer has been recorded.
06 / Filed and follow-upFinish the engagement properly.
Filed returns with the e-file acknowledgement that was recorded and the next-year organizer that was sent, each with its date.
07 / InsightsTurn a count into the next return.
Status counts, the deadline risk count and the outstanding document count all filter the same records, so a number opens the returns behind it.
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.
- Tax return engagements · 7 stages
- New client onboarding · 7 stages
- Extensions and late filings · 6 stages
- Business return engagements · 6 stages
Give the next step a shape.
- Engagement start
- Document request
- Ready to prepare
- Review assignment
- Signature request
- Filed note
- Next-year organizer
- Missing document follow-up
- Extension reminder
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 14 fictional return engagements with 96 recorded documents, two recorded extensions and three returns inside the deadline risk window. 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.
- New client tax intake
- Document checklist request
- Engagement feedback
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Three reusable templates.
- Missing documents request sheet
- Return review checklist
- Filing summary cover sheet
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 opportunity is one return engagement for one client and one tax year. It holds the client label, return type, preparer and reviewer labels, status, filing deadline, extension, e-file acknowledgement, next-year organizer, an optional fee reference, document rows and an editable return checklist.
Document intake grid with per-return-type column sets
Returns ledger operating view
Missing documents operating view
Deadlines operating view with extension handling
Review queue operating view
Filed and follow-up operating view
Insights operating view with actionable filters
Three native form drafts and three editable document templates
Editable per-return checklists and preserved document row history
Four optional pipeline templates and nine inactive workflow drafts
14 fictional in-memory return 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 practice 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 record creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, enforce the document and deadline rules, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
The grid records that a document arrived; it does not store the document. Taxpayer identification numbers are refused in every field, and no included form asks for one. The kit does not calculate tax, give advice, prepare or check a tax form, file anything, connect to a tax authority, collect a signature, take a payment or message a client.
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?+
Ledgerday keeps one black masthead 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