Skip to content
Edishan Lee TenorioAI Automation Specialist & CRM DeveloperSoftware Engineer · Full-Stack Developer · Mobile Developer

02 · Full-stack product + automation

Jackson Properties: Real Estate Platform & Built-in CRMFrom a homeowner's first click to a signed contract, in one system.

A direct-purchase real estate platform for a Cedar Park, Texas team: a seller site that shows the offer math up front and turns wary homeowners into structured leads, a homes page with a buyer list, and a built-in CRM where every lead is nurtured and tracked to closing.

Client
Jackson Investment Group
Year
2026
Status
Live in production
Jackson Properties CRM: pipeline summary cards, stage filters, and a kanban board with New, Contacted, Appointment set, Offer made, Under contract and Closed columns. Lead details are blurred for privacy.
  1. 1Pipeline health: totals, new this week, under contract, due today
  2. 2Seven stages, from new lead to closed or dead
  3. 3Drag-and-drop kanban to move deals between stages
  4. 4Leads segmented by source and quality
  5. 5Priority sort by lead quality and contact signals
Seller intake, about 90 seconds
4 steps
Pipeline stages, new lead to closed
7
System for sellers, buyers and the pipeline
1

01Problem

A direct-purchase team wins deals on speed and trust. Sellers in a hurry don't wait, so every lead has to be answered fast, followed up consistently, and tracked until the house either closes or the lead goes cold.

The "we buy houses" category has earned homeowners' distrust: lowball offers, black-box numbers, pressure to sign. The site had to win a property file from people who are wary by default, and the business needed a second side too, a way to line up buyers for the homes it renovates. Generic CRMs model sales pipelines, not property deals.

02My role

Full-stack engineer, public site, CRM and automation

  • Seller site with a 3D hero, offer calculator and service-area map
  • Multi-step property-file intake
  • Homes for sale page and buyer list
  • Laravel backend and lead data model
  • Internal CRM: pipeline, kanban and filters
  • Lead nurture and follow-up automation

03System architecture

The public site is built to load fast and earn trust: a Three.js hero, then small, focused pieces for the offer math, the map and the intake. Behind it, one Laravel API owns the lead record, so a seller's property file, a researched list entry and a buyer sign-up all land in the same system the team works from.

  1. 01 Attract

    Seller site

    • 3D house hero, local pitch
    • Offer formula you can check
    • Service-area map, foreclosure help
  2. 02 Capture

    Property file intake

    • 4-step form, ~90 seconds
    • Live seller-record preview
    • Lead created via API
  3. 03 Nurture

    Built-in automation

    • Lead ID + source tagging
    • Follow-ups and due actions
    • Priority by quality + contact
  4. 04 Close

    CRM pipeline

    • 7-stage kanban
    • Offers and contracts tracked
    • Archive and CSV export
  5. 05 Resell

    Homes + buyer list

    • Renovated homes page
    • Buyer-list sign-up
    • Buying method + wish list captured

Across every stage

  • Laravel REST API
  • Authenticated CRM
  • Three.js hero
  • Form input hidden from analytics

04Implementation

  1. 02.1

    Show the math, not a black box

    The homepage puts the offer formula on screen: value after repairs, times the ratio, minus repairs. Sellers change the numbers and watch the cash offer move, then compare it with what fixing and listing would cost them in commission, closing costs, repairs and holding costs. It is labeled as an illustration, not an offer.

  2. 02.2

    A form that feels like opening a file

    Instead of a generic contact form, sellers open a "property file": four short steps that start with just the street address. A seller-intake record fills in beside the form as they type, so they can see exactly what they're sharing.

  3. 02.3

    Local, and able to prove it

    An interactive service-area map is centered on Cedar Park: hover a town to see how far it is. County lists, the neighborhoods the team knows, a foreclosure and bankruptcy section, and a plain "when you shouldn't sell to us" section all answer the questions wary sellers actually have.

  4. 02.4

    One lead model, every source

    Website inquiries and researched property lists land in the same Laravel-backed lead record, each with a market-coded ID (AUS-2026-…) and a source tag, so the team can filter direct inquiries, scraped lists and high-quality leads.

  5. 02.5

    A pipeline built around how deals move

    Seven stages from New to Closed or Dead, as a drag-and-drop kanban or a board view. Quick filters surface what's due today, what's mine and what's under contract, and built-in automation tracks follow-ups and ranks leads by quality and contact signals.

  6. 02.6

    Both sides of the business

    A homes-for-sale page lists renovated houses with what was fixed, and a buyer list captures each buyer's contact, how they're buying and what they're looking for, so the team can reach them before a home is listed.

05Outcome

  • Live at jacksonproperties.us, based in Cedar Park and serving Travis, Williamson and Hays counties
  • Seller acquisition, the buyer list and deal management run in one system the team owns
  • Every lead visible in a single pipeline, from intake to closing
  • Follow-ups and due actions surfaced automatically instead of tracked by hand
  • Next.js
  • Laravel
  • Three.js
  • REST API
  • Workflow automation
  • Microsoft Clarity
Visit the live product

06Screens

Jackson Properties homepage: 'Sell your house as-is, on your date, with a number you can check,' beside a 3D low-poly house, with 0% commission, $0 repairs and 10–14 days to close.
Fig. 01Seller site: a Three.js house and a promise sellers can check.
Offer calculator: value after repairs times 70% minus repairs equals a rough cash offer, beside a fix-and-list cost breakdown with sliders.
Fig. 02The offer formula, live. The figures are the site's own illustration.
Service-area section: Cedar Park home base, same-week walkthrough areas, neighborhood chips and an interactive map of nearby towns.
Fig. 03Interactive service-area map, centered on Cedar Park.
Four-step 'Open a property file' form beside a seller intake record filling in as the seller types.
Fig. 04Property file intake: the record fills in as the seller types.
Buyer list form: name, buying with, email, phone and what the buyer is looking for.
Fig. 05Buyer list: buyers hear about each home before it's listed.

Next step

Have a process that should be automated?

Tell me about the workflow that's slowing you down, the systems you need connected, or the application you want to build. We'll work out the right approach.