# Build brief — a focused alternative to LeaseLineage

> **Verdict:** Partly, if you narrow it · **Buildability:** 36/100 · **Category:** Automation
> **Source:** https://www.canitbevibecoded.com/leaselineage
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from LeaseLineage. Verify current pricing and capabilities before acting.

## Context

**LeaseLineage** — Prospecting, outreach campaigns, tenant demand, and deal tracking for commercial real estate brokers. It currently costs $79/mo.

A solo broker can build the CRM, CSV prospecting, draft sequences, and pipeline in a contained effort, but reliable contact data, Gmail and Outlook sync, deliverability, compliance operations, and brokerage collaboration are ongoing products.

This brief describes a focused, single-operator replacement for the part of LeaseLineage that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Import or research prospects, organize them by property or tenant need, draft a reviewed email sequence, and track replies and deal stages.

- Automate a small number of known workflows with logs, retries, and manual recovery.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Local web app.
- SQLite.
- CSV import.

### Data and integrations

- OpenAI API key.
- Optional SMTP credentials.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a local commercial real estate outreach workspace to replace LeaseLineage. Requirements:

- A local web app using Node, Express, better-sqlite3, and server-rendered EJS,
  with a little vanilla JavaScript; store everything in data/leaselineage.db.
- Import prospects from CSV with company, contact, title, email, market, asset
  class, property, source, and notes; deduplicate by lowercase email.
- Show a prospect table with search, filters, tags, and a detail page containing
  notes, activity history, and a next-follow-up date.
- Let me create a campaign from filtered prospects and draft a three-step email
  sequence with the OpenAI API; keep its key and optional SMTP credentials in .env.
- Every generated message must remain a draft until I approve it. Support test-send,
  scheduled send, daily send limit, unsubscribe footer, and a suppression list.
- Poll one IMAP inbox every five minutes, match replies by Message-ID and email,
  stop remaining steps for that prospect, and show replies in a unified inbox.
- Track opportunities on a kanban board with New, Contacted, Replied, Meeting,
  Proposal, Won, and Lost columns; moving a card writes an activity event.
- Provide CSV exports for prospects, campaigns, activities, and opportunities.
  Bind to localhost only; no accounts or telemetry beyond email and OpenAI calls.
- Out of scope: contact-data enrichment, Gmail or Outlook OAuth, multi-user teams,
  custom sending domains, and legal compliance guarantees.
- Include a README with setup, CSV columns, .env variables, IMAP app-password notes,
  backup instructions, and a warning that I remain responsible for lawful outreach.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Apollo and Hunter prospect data.
- Gmail and Outlook OAuth and reply sync.
- Managed sending and deliverability.
- Brokerage team workspace.
- The useful dataset is owned, accumulated, or expensive to reproduce.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Mautic](https://github.com/mautic/mautic) — Open-source marketing automation platform that covers campaigns and contact management, without the commercial real estate workflow

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/leaselineage