Build it into your Seedly.

Download the module and integrity manifest from /portal/downloads/goseedly-real-estate. Sign in with your purchase email, or the email on your active DevLaunch All Access membership. The optional Agent Kit and CRM Kits All Access subscription are separate products.

• A separately licensed Seedly source checkout. The current installer accepts 5.8.4–5.8.x; 5.8.4 is the validated reference. Check your exact version and customizations.
• The extracted Real Estate module archive and its adjacent checksum manifest. Keep the previous release and your source backup.
• The designated test Convex deployment, corresponding frontend URL, and an authorized Seedly operator.
• Your location’s public ID and the existing pipeline and open stage you want new property inquiries to enter.

The Real Estate Agent kit is optional. Neither product requires the other. Provider credentials are optional for manual properties, photos, pages, and inquiries.

node bin/install.mjs --seedly /absolute/path/to/seedly
node bin/install.mjs --seedly /absolute/path/to/seedly --apply
node bin/doctor.mjs --seedly /absolute/path/to/seedly

Read QUICKSTART.md, docs/SEEDLY_INTEGRATION.md, and the host’s AGENTS.md before applying changes. Verify the archive SHA-256 against its manifest. Resolve customization conflicts deliberately; preserve unrelated edits and module receipts.

Source installation is separate from deployment. Generate the complete Convex API using the host’s documented workflow and designated test deployment. Run the package’s installed-host checks, backend/web type checks, production web build, and post-build type check. Deploy backend changes before the frontend through your host’s release process.

Use docs/CONVEX_SETUP.md for the exact backend integration. Do not create a second auth system, contact database, or copy of the companion kit. The installer does not activate inquiry routing, paid providers, or workflows.

Install the supplied GoSeedly Real Estate module into my licensed Seedly checkout.
Module directory: [absolute extracted module path]
Seedly directory: [absolute host source path]
Test deployment and frontend: [designated targets]
Location public ID: [location]
Intake pipeline and open stage: [existing destination]
Companion kit present: [yes/no]

Read host AGENTS.md, module QUICKSTART.md, and docs/AGENT_INSTALL.md.
Follow SEEDLY_INTEGRATION.md, CONVEX_SETUP.md, CRM_INQUIRIES.md,
and WORKFLOW_AUTOMATIONS.md. Verify the package checksum and versions.
Preserve existing source changes and receipts. Preview installation,
apply supported changes, and run doctor and the documented host checks.
Use the existing login, Convex, Files, contacts, and opportunities.
Do not infer a deployment target. Keep deployment pending if none is given.
Test with synthetic records: property, photos, publication, signed-out
inquiry, contact match, pipeline placement, and duplicate prevention.
Check location boundaries and restricted roles with real sessions.
Verify linked property photos, listing prices, addresses, and facts on
native pipeline cards and drag previews. Keep opportunity values intact.
Review a native workflow in dry run, then test an internal property note
action, replay prevention, and a failure branch. Do not enable outreach.
Report commands, results, pending provider checks, and rollback steps.

The full acceptance sequence and recovery requirements are in the package’s docs/AGENT_INSTALL.md. A coding agent can assist with source setup; it still needs the correct accounts, permissions, credentials, and designated deployment.

1. Choose an existing native pipeline and an open intake stage. Enable Accept property inquiries and save CRM routing. The operator needs Real Estate administration update and native Contacts and Opportunities view/create permissions.
2. Publish a small manual collection. Open it signed out and submit a synthetic question or tour request with explicit contact-sharing consent.
3. Confirm the matching or new contact, the reused or new opportunity, the configured pipeline/stage, the property links, and the request activity in Seedly.
4. Repeat the request and check deduplication. Confirm existing contact preferences and opportunity values/stages remain intact. Test disabling intake and unpublishing the collection.

The installer adds property details to native pipeline cards and drag previews. Link a property to an opportunity to show its cover photo, listing price or monthly rent, address, beds, baths, and area. Property prices do not replace the opportunity value. Archived or inaccessible properties are hidden.

Routing applies to published collections in the selected location. New opportunities are unassigned unless you configure native assignment actions. A tour request is not a booked calendar appointment or marketing opt-in.

Follow the credentials and test steps in the selected provider’s setup UI and docs/PROVIDERS.md. Configure the server encryption secret through the documented Convex setup, set a location request budget, then explicitly test the connection. Keep keys out of frontend code and installation reports.

A local demo response does not test a live MLS account. Record live access as pending when credentials are unavailable. Saved provider results do not automatically refresh; public collections accept manual listings, not a public MLS IDX feed. Provider accounts, fees, permissions, and display rights are separate.

The installer registers the workflow extensions and template definitions. Seeding the native template gallery and activating a workflow are separate operations. Follow docs/WORKFLOW_AUTOMATIONS.md and review the target and seed scope first.

• Start with a synthetic contact and Load property → Add property note.
• Verify dry run skips writes, replay does not duplicate effects, and a wired failure branch handles errors.
• Verify the executing author’s permissions and inspect native execution history.
• Keep outbound messaging absent from installation tests. Configure and activate follow-up separately.

1. Add manual properties and upload permitted photos through Seedly Files. Set cover order, descriptions, and crop focus.
2. Create a named collection and choose Classic, Editorial, Gallery, Directory, Spotlight, or Portfolio.
3. Choose Full page, Search + listings, or Listings only. Adjust branding, layout, card appearance, photo shape, density, sorting, and visible facts.
4. Select and order up to 24 manual properties. Preview desktop, tablet, and phone. Save the draft, review changes, confirm display rights, and publish.
5. In Share, copy the public URL or generated iframe. Paste the iframe into your existing site’s HTML/embed block and set a suitable height. Test on the actual destination page, including phone scrolling and property details.

You can create up to 20 independent collections per location. Embeds use a configured height; automatic iframe resizing and custom-domain automation are not included. Test the published page signed out. Unpublishing makes its public page and embed unavailable.

Keep .seedly-addons/real-estate/receipt.json, the archive and manifest, and your source backup. Use docs/OPERATIONS.md for upgrades, recovery, and removal. Source rollback is not database rollback: native contacts, opportunities, files, inquiry records, and workflow receipts are customer data.

Before retiring the module, pause dependent workflows, address pending executions, disable inquiries, and unpublish every collection. Preserve schema/data compatibility and do not remove CRM records or files just to make an uninstall pass.

• docs/USER_GUIDE.md and docs/PUBLIC_PAGES.md — everyday use and publishing.
• docs/CRM_INQUIRIES.md and docs/WORKFLOW_AUTOMATIONS.md — native CRM and workflow behavior.
• docs/API_REFERENCE.md and docs/examples/seedly-integration.tsx — developer contracts and a typed host example.
• docs/COMPANION_KIT.md — independent or combined kit use.
• docs/VALIDATION.md and docs/CHANGELOG.md — checked behavior and release history.