Skip to content
View packages
CRM Kits Boarding and lesson barns

GoSeedly Equestrian Stable Kit

Every stall.
Every farrier date.

A barn board for boarding and lesson barns: every aisle drawn as its stalls, each horse with its feed, hay and turnout labels and its next farrier and vet visit, and today's lesson book beside it. Crosstie keeps a seven-day lesson book, farrier and vet visits week by week with farrier cycles as recorded, boarders and lesson families, riders by first name and age band, and the feed chart in one connected workspace. It gives no veterinary or riding advice and keeps no rider ages, schools or health details.

Checking access…See the interface
One-time purchase · USD · Your Seedly backend · Editable kit source

YOUR CROSSTIE WORKSPACE

01 — BARN BOARD
Damson top bar with rope-underlined tabs and a crosstie mark over a needs-attention strip of four barn clients, an aisle of stall cards with feed, hay, turnout and next farrier and vet visits, and a lesson book for today and tomorrow, alerts flagged in red, using fictional sample data

Actual interface captures with fictional sample data. Open a screenshot for a closer look.

TAKE A CLOSER LOOK

Built around the stall, the lesson and the visit date.

One connected workspace, with views built around the decisions your team makes each day.

Barn board in the GoSeedly Equestrian Stable Kit with fictional sample records01 / Barn board

See every stall in the barn at a glance.

Each aisle as a row of stall cards with the horse, owner, board kind, AM and PM feed and hay labels, turnout and the next farrier and vet visit, paddocks and pasture below, and today's and tomorrow's lessons beside it. Visits past their date, requested visits in the next three days, farrier cycles passed with nothing booked and lessons with no instructor lead the page.

Lessons in the GoSeedly Equestrian Stable Kit with fictional sample records02 / Lessons

Run the lesson book seven days out.

One column per day with every booked lesson in time order, its rider, horse, ring and instructor, then each instructor's booked lessons and minutes in two separate columns and the lessons marked done, cancelled or no-show.

Farrier and vet in the GoSeedly Equestrian Stable Kit with fictional sample records03 / Farrier and vet

Keep farrier and vet days week by week.

Visits still open after their date first, then six weeks of farrier, vet, dentist and bodywork visits with the stall, provider, status and who holds the horse, and a farrier cycle ledger from each horse's last recorded visit and interval.

Clients in the GoSeedly Equestrian Stable Kit with fictional sample records04 / Clients

Move every inquiry into a stall or a lesson slot.

Inquiry, waitlist, active and leaving lanes with each client's horses and stalls, riders by age band, the guardian for minor riders, booked lessons, the next visit, the recorded board per month and the rate per lesson.

Riders in the GoSeedly Equestrian Stable Kit with fictional sample records05 / Riders

Keep riders to a first name and an age band.

Every rider as a first name and last initial with the age band, minors marked in words with their guardian, the level label, the client, booked lessons this week and the last lesson ridden.

Feed and turnout in the GoSeedly Equestrian Stable Kit with fictional sample records06 / Feed and turnout

Print the feed chart the barn already writes.

AM feed, PM feed, hay, turnout and paddock for every horse by aisle and stall, exactly as the barn writes them, then turnout groups by paddock. Scoops and flakes are labels and are never totalled.

Insights in the GoSeedly Equestrian Stable Kit with fictional sample records07 / Insights

Read each ledger in its own unit.

Clients by kind and status, horses by status and aisle, riders by age band, booked lessons by kind, booked minutes by instructor, visits by kind and recorded board by client kind. Horses, lessons, minutes and dollars are never added together or drawn on one scale.

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.

01 / FOUR PIPELINES

Choose your starting structure.

Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.

  1. Boarding clients · 8 stages
  2. Lesson riders · 7 stages
  3. Training board · 7 stages
  4. Move-outs and stall turnover · 7 stages
02 / NINE WORKFLOW DRAFTS

Give the next step a shape.

  • Barn tour follow-up
  • Move-in preparation
  • Arrival setup
  • Trial lesson follow-up
  • Package renewal
  • Evaluation notes
  • Progress update
  • Move-out steps
  • Stall ready

Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.

03 / SAMPLE WORKSPACE

Explore before adding records.

Explore 12 fictional barn clients: eleven live (eight active, one leaving, one on the waitlist, one inquiry) and one closed, with 13 horses, 11 riders (6 of them minors), 24 lessons, 24 farrier, vet and other visits and 96 checklist steps. 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.

01 / INTAKE & FOLLOW-UP

Three ready-to-edit forms.

  • Riding lesson inquiry
  • Boarding inquiry
  • Farrier or vet visit request

Choose forms individually in Setup & resources, then customize and publish them in the native form builder.

02 / WORKING DOCUMENTS

Three reusable templates.

  • Board and care sheet
  • Lesson package summary
  • Farrier and vet day list

Open each template in Documents and complete it for the actual job or visit.

03 / THE NEXT STEP

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 barn client holds the owner, the guardian for minor riders, the client kind and status, the start date, the recorded board per month and rate per lesson, every horse with its aisle, stall, paddock, turnout, AM and PM feed and hay labels, farrier interval and status, every rider as a first name and last initial with an age band and level, every lesson with its date, time, minutes, instructor, horse, ring and status, every farrier, vet, dentist and bodywork visit with its provider, date, status and who holds the horse, and an editable checklist.

Barn board operating view
Lessons operating view
Farrier and vet operating view
Clients operating view
Riders operating view
Feed and turnout operating view
Insights operating view
Three native form drafts and three editable document templates
Editable client checklists and preserved row history
Four optional pipeline templates and nine inactive workflow drafts
12 fictional in-memory barn clients
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.

01

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.

02

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.

03

Set up your own team.

Edit barn 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 client creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, keep every figure in its own unit, hold riders to a first name and last initial with a guardian for every minor, refuse rider ages, schools and health details, dates of birth, access codes, passes, logins, bank details, card numbers and Social Security numbers, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.

Crosstie records stalls, feed, turnout, lessons and visit dates as the barn typed them. It gives no veterinary, farrier, riding, safety, insurance or liability advice, does not say a horse is sound or suited to a rider and does not recommend a farrier interval, a ration or a turnout; a farrier cycle date is the recorded interval added to the recorded last visit. It is not a veterinary record, a waiver or a boarding contract, bills nothing, takes no payment and sends no messages. Dates of birth, exact ages, school names and rider medical, injury and allergy details, gate, barn and tack room codes, passes and logins, owners' bank details, card numbers and Social Security numbers 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.

Checking access…

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 Access

Already 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?+

Crosstie keeps its damson top bar with rope-underlined tabs, serif nameplate headings and the crosstie mark 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.

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.

Customer experiences / Trustpilot

What customers say
about DevLaunch.

Read all reviews on Trustpilot ↗

Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.