GoSeedly Podiatry Kit
A week-grid recall planner above a custom order pipeline: nine columns of patient chips from past due through seven weeks ahead, and one row per order with five step dots running from ordered to fitted. Footing keeps the front desk work in one connected workspace and leaves clinical records in the practice's own system.
YOUR FOOTING FRONT DESK
01 — DESK
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 / DeskNine columns stack every recorded next recall week: a pinned past-due column on the left, then this week and the seven weeks ahead. Each chip carries the recall category, the interval in weeks, and booked or not booked yet in words with a filled or hollow square beside it.
02 / Order pipelineThe second half of the desk. One compact row per order, with a run of five dots joined by a single rule filling through ordered, at lab, received, fitting booked and fitted, beside the days at the current step, the lab label and the quoted turnaround.
03 / PatientsReview the age band label, the preferred contact window, the recall category and interval, the next recall week, open orders, reorders due and the derived desk state.
04 / Recall plannerThe same grid with the recorded contact attempts and last contact date on every chip, above a ledger of every recorded recall. Recording a recall does not contact anyone and does not book anything.
05 / Custom ordersOpen orders by days at the current step, with the office order label, the lab, the ordered date, the quoted turnaround and the recorded reference amount. An order still out past the quote is marked and is one of only two reds in the kit.
06 / Fittings dueOrders back from the lab with no fitting date recorded, then the fittings already booked and still ahead. Booking happens in the practice's own calendar; the kit records that it happened.
07 / Supplies and reordersRetail product labels with their recorded reorder reminder dates inside the reorder window, soonest first. The window is a workspace value the practice records for itself, saved with a revision guard.
08 / InsightsEach derived desk state, plus recalls on the grid, open orders, fittings to book and reorder reminders due. Open the patients behind any number. Nothing is forecast or projected.
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 18 fictional patients with 16 recalls across the eight-week grid, 4 of them past due and 7 not booked yet, 11 custom orders across all five steps with 2 past the lab's quoted turnaround, 3 orders waiting for a fitting to be booked and 6 supply reminders. 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.
PLEASE READ
THE KIT, UNPACKED
One contact-linked record is one patient relationship. It holds the patient label, an age band label, the preferred contact window, the recall category, the recall interval in whole weeks, the next recall week start, whether the recall is booked, the contact attempts and last contact date, custom orders with their office label, lab label, step and dates, retail supply reminders and an editable front desk 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 practice 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 record creation, edits, the recorded reorder window and resource setup. They preserve native account permissions, unrelated custom fields and row history, check revisions before saving, and run the clinical guard before anything is written. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
This is a front desk and custom order record, not a medical record. It is not a HIPAA compliance product, it is not an EHR, EMR or practice management system, and installing it does not make a practice HIPAA compliant. Do not use it to store protected health information. It never stores diagnoses, conditions, anatomy or side references, wound or nail descriptions, diabetic status or risk categories, gait or pressure findings, device specifications, casts or scans, a shoe size as a clinical measurement, medications, medical history, insurance member or policy numbers, authorization numbers, government identifiers or dates of birth. The shared model refuses free text that reads like one of those in every field, on the server as well as in the browser, and names the rule it matched; ordinary front desk phrases and retail product labels are accepted. Treat that as a guard against accidental entry rather than a guarantee. Clinical records stay in the practice's own system, and the kit gives no medical or footwear advice. The practice is responsible for its own compliance and for whatever it chooses to record in its CRM. There is no practice management integration, no clinical or device record, no lab ordering integration, no insurance, authorization or billing, no scheduling engine, no automated reminders or patient messaging, no patient portal and no payments.
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
No, and it does not claim to be. It is not a HIPAA compliance product, an EHR or a practice management system, and installing it does not make a practice compliant. It is a front-desk and relationship workspace for recalls, reminders, follow-up and intake progress. Keep clinical notes, diagnoses, prescriptions, test results, insurance details and other protected health information in your clinical system. The kit runs on your own Seedly CRM; DevLaunch does not host, receive or process your patient data, and your practice remains responsible for its own privacy, security and regulatory obligations.
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.
Footing keeps its slate rail 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.