Skip to content
View packages
CRM Kits Mortgage brokers

GoSeedly Mortgage Broker Kit

Every file complete.
Every lock on time.

A loan file is late for one of three reasons: a document has not arrived, a milestone has not moved, or the rate lock is about to expire. Keystone puts all three on every row of one white board, under a teal-blue chrome bar, so you can read twenty files without opening any of them.

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

YOUR KEYSTONE LOAN FILE BOARD

01 — LOAN FILE BOARD
Mortgage broker loan file board with document checklist strips, milestone chips, and rate lock countdowns using fictional sample data

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

TAKE A CLOSER LOOK

From the first document to the closing date.

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

Loan file board in the GoSeedly Mortgage Broker Kit with fictional sample records01 / Loan file board

Read the whole pipeline in one pass.

Each row carries the borrower label, a loan purpose chip, the document checklist strip, the recorded milestone, the loan amount reference and the rate lock countdown. Selecting a row opens the file sheet beside the board, so the row stays in view while you read its record.

Pre-approvals in the GoSeedly Mortgage Broker Kit with fictional sample records02 / Pre-approvals

Know which letter lapses first.

Files with a recorded pre-approval letter, ordered so the one closest to its recorded expiry comes first. An expired letter is marked in red. Nothing expires on its own and no letter is generated here.

Rate locks in the GoSeedly Mortgage Broker Kit with fictional sample records03 / Rate locks

Put the countdown in order.

Recorded locks grouped into expired, under seven days, seven to thirty, and later, measured from the working date you choose. Files with no recorded lock are listed separately as unlocked rather than given an invented countdown.

Referral partners in the GoSeedly Mortgage Broker Kit with fictional sample records04 / Referral partners

See who sends you the work.

Recorded referral partner labels with their file counts, how many are still open, and the loan amount reference total reported once per currency. Files with no recorded label keep their own stated row.

Closings in the GoSeedly Mortgage Broker Kit with fictional sample records05 / Closings

Know what lands, and when.

Files grouped by recorded closing date against the working date, with the document strip beside each one so you can see what is still outstanding before the day itself.

File insights in the GoSeedly Mortgage Broker Kit with fictional sample records06 / File insights

Read the files honestly.

Milestone mix, loan purpose mix, recorded document completion with its denominator stated, and lock position counts. Loan amount reference totals are reported once per currency present and never added across currencies.

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. Purchase loans · 8 stages
  2. Refinance loans · 7 stages
  3. Pre-approvals · 7 stages
  4. Referral partners · 7 stages
02 / NINE WORKFLOW DRAFTS

Give the next step a shape.

  • Application intake review
  • Document request note
  • Missing documents follow-up
  • Appraisal ordered review
  • Conditions check
  • Rate lock expiring review
  • Clear to close note
  • Closing day check
  • Post-closing review note

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 ten fictional loan files across all seven milestones, with 63 document checklist items, two rate locks already under seven days and four recorded pre-approvals including one expired. Sample edits stay in the current page’s memory and reset on navigation or reload; sample files are never inserted into your CRM.

No sample customers are inserted into your CRM.

Starter setup checks selected kit additions before removal and preserves edited records and live work.

THE KIT, UNPACKED

Your workspace.
Your starting point.
Your code to edit.

A loan file is a native contact-linked opportunity with namespaced borrower and co-borrower labels, loan purpose, program label, a loan amount reference in integer minor units, a free-text rate reference, lender and referral partner labels, the recorded milestone, rate lock dates, pre-approval dates, a closing date, file notes and document checklist items with stable IDs. Other custom fields are preserved, and archived checklist items are kept rather than dropped.

Two-pane loan file board with a per-row document checklist strip and file sheet
Rate lock and pre-approval countdowns derived from a working date you choose
Referral partner rollup and closing bands from recorded dates
File insights with stated denominators and per-currency totals
Teal-blue Keystone application frame on a white canvas with full CRM tools
Four optional pipeline templates and nine inactive workflow drafts
Ten fictional in-memory loan files with 63 document checklist items
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 brokerage 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 loan file helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, and checks the current record timestamp and revision before saving. It deliberately exposes no stage mutation, so a stage change goes through your own Seedly move function under its own permission. Deploy the helper from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional and no schema migration is required.

This is not a loan origination system. There is no 1003 or URLA, no automated underwriting, no agency submission, no credit pull, no credit score, no income or asset figure, no debt ratio, no account number, no pricing engine, no rate sheet, no APR or payment calculation, no document storage, no upload, no e-signature and no disclosure generation. It makes no compliance guarantee: TRID, RESPA, ECOA, HMDA, state licensing and record retention stay entirely yours. It integrates with no lender, so a recorded rate lock is a note about a lock you took elsewhere and nothing is locked, extended, repriced or confirmed here. It orders no appraisal or title work and messages no borrower or partner. The recorded milestone is a staff entry independent of the native pipeline stage, and saving file details never moves a deal. A checklist item records that a named document arrived; document completion is received divided by recorded items with archived rows excluded, and no recorded item gives no ratio rather than a zero. Closing dates are recorded plans, not confirmed appointments or Calendar events. The loan amount reference is a recorded planning number, separate from opportunity value, commission, invoices and 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.

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

Keystone keeps its loan file navigation across the original broker 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.

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.