How the system fits together

The Smith Douglas software stack is one shared SQL Server database (SmithDouglasCommunities) surrounded by a family of applications. Each app exists for a different audience — corporate users, builders in the field, trade partners, and home buyers — but they all read and write the same data.

The 30‑second mental model

                ┌──────────────────────────────────────────────┐
                │     SmithDouglasCommunities (SQL Server)     │
                │   ~600 tables · ~360 views · 14 companies   │
                └──┬─────────┬─────────┬─────────┬─────────┬───┘
                   │         │         │         │         │
        ┌──────────┘         │         │         │         └────────────┐
        │                    │         │         │                      │
   ┌────▼────┐         ┌─────▼────┐ ┌──▼──────┐ ┌▼──────────┐    ┌──────▼──────┐
   │ SMART 1.0│         │ SMART 2.0│ │ Portals │ │  Warranty │    │ BC Worker   │
   │ desktop │         │   web    │ │  (3)    │ │  (Blazor) │    │  (sync→BC)  │
   └─────────┘         └──────────┘ └─────────┘ └───────────┘    └──────┬──────┘
                                                                        │
                                                                        ▼
                                                              Business Central
                                                                (Microsoft cloud ERP,
                                                                 live since Jan 2026)

The applications, in plain English

SMART 1.0 (desktop)

The core enterprise application. Sales, Production, Project Management, Service, Accounting, Product Development, Administration — everything runs through it. Built in C#/.NET (WinForms + WCF), source under SOURCECODE/SMART/src2021.

SMART 2.0 (web)

The browser version of SMART (thesmartbuilder.net). Handles many of the same line-of-business workflows as SMART 1.0 (sales, production, accounting, land, project management, service, web reports, AgilePoint BPM) plus the App_API/ endpoints the portals call. ASP.NET Web Forms; source under Workplace2020/.

Builder Portal

A mobile-friendly Web Forms site for field superintendents to view schedules, approve trade work (spProcessPaymentReview), review POs, and submit delay requests (email to area manager). Source: BuilderPortal/BuilderPortal2024/.

Trade Portal

The site trade partners log into to see open POs, schedule visits, submit lien waivers, and accept change requests.

Home Owner Portal

What buyers and home owners use to track their schedule, see selections, submit warranty requests, and upload pictures.

Blazor Warranty Service

The web app the Customer Service Reps (CSRs) use to triage Service Requests, generate Service Orders, and track aging items.

BC Integration Worker

A .NET 9 Windows Service that synchronizes posted vendors, invoices, payments, and ledger entries between SMART and Business Central (Microsoft’s cloud ERP — our financial system of record since January 2026). Runs every 5 minutes.

How information moves

Selling a home

1. Marketing drives traffic into a community.
2. A buyer becomes a Contact, picks a Lot and a Plan.
3. Sales creates a Contract (status qte Quoted → lr Lot Reserved → acc Accepted → rat Ratified → clo Closed).
4. Once Ratified, the lot is locked, the schedule is generated, and the build starts.

Building a home

1. The lot’s Plan + Selected Options drive an Estimate (cost).
2. The estimate becomes Purchase Orders for trades.
3. Schedules are built from Standard Plans. Critical Activities mark major milestones; Delays push everything that depends on them.
4. Trades work through the Trade Portal; the builder approves work through the Builder Portal (WorkApproval.aspx → spProcessPaymentReview), which queues TransmissionPOApprove for the BC worker.
5. The BC Integration Worker picks up new Transmission rows and posts them to Business Central.

After the close

1. The home owner submits a Service Request through the Home Owner Portal, phone, or email.
2. CSRs use the Blazor Warranty app to break the request into ServiceRequestLine items, each with a ServiceRequestLineStatus.
3. Lines that need a trade get a Service Order with a deadline; the trade is paid via a SO Number flowing through the same BC pipeline.

Environments

Environment	SQL Server	Database	Purpose
Production	SDHDCSQL01	SmithDouglasCommunities	Live business data
Test	SDH-DC-SQLTST01.thesmartbuilder.local	SmithDouglasCommunities	Dev/QA — what these docs use
QA	SDH-DC-SQLQA01	SmithDouglasCommunities	UAT before release

Tip

Reference counts and schema lists were last refreshed against Test: server SDH-DC-SQLTST01.thesmartbuilder.local, database SmithDouglasCommunities (2026-06-02). Structure and lookup data match Production; row counts do not.