Next steps

Whatever Tech / Proposal

One platform.
Every home after handover.
Built once, grown in steps.

The AB Client Experience Portal in phases. Phase 1 puts warranty and estate management in your homeowners’ hands, in AB’s own app on the App Store and Google Play, for US$28,000. Offline field work, payments, marketing and AI are add-ons you switch on when you’re ready, on the same platform, with nothing rebuilt.

proposal / ab-client-experience / v2.0Draft
Client
Arzuman Brothers
Project
AB Client Experience Portal
Phase 1
Warranty service, estate management pilot and native apps, US$28,000
Full vision
US$49,300 in four steps
Status
Draft for review
Version
2.0, November 18, 2026
Replaces
Technical proposal of November 6, updated with the November 13 review
Part 1

The plan, in plain words.

What we build, in what order, what it costs and what your homeowners get at each step. Part 2 holds the technical scope that backs every line here.

01 / Summary

What we’re building and why now.

Next year AB starts delivering more homes, and with them a wave of warranty requests and maintenance needs. Today that runs on email, phone calls and monday boards. The portal brings it into one place before the wave arrives.

In plain words

One “brain” for everything that happens to a home after handover. Homeowners use an app to see their coverage, request repairs and book services. The field team uses the same app to record visits. AB’s team runs it all from a web workspace. Every piece reads and writes the same data, so adding the App Store version, offline mode or payments later plugs in instead of starting over.

W

Homeowners who built with AB

Their warranty is set up at handover from the trades actually built. They see what’s covered and until when, which maintenance keeps it valid, and they open a request with photos instead of calling.

E

Estate management clients, AB-built or not

Any homeowner can buy a one-off service, such as pressure washing the trash bins, or subscribe to a maintenance tier and add à la carte services. For homes AB didn’t build, this is a standalone product.

Phrases you’ll stop hearing.

What you hear today

  • “I sent photos of the leak by email last week, did anyone see them?”
  • “Is this covered by my warranty?”
  • “When is the crew coming? Nobody confirmed.”
  • “The supervisor was here, but we have no record of what he did.”
  • “I didn’t know I had to clean the roof drains.”
  • “Can someone just come once a month for the bins?”

What changes with the portal

  • Every request lives in one case, with photos, messages and history.
  • Homeowners see what’s covered and until when, before they call.
  • Visits are booked from suggested dates and confirmed by SMS.
  • Each visit is verified by the homeowner, with notes and photos.
  • Maintenance due dates are visible before they affect coverage.
  • Services and plans are one tap away, with upsells built in.

Separate project. The call outreach app (dialer) is already approved and isn’t priced here. It is built as a module of this same portal: the portal reuses its login and its RingCentral connection, and the marketing add-on can feed it call lists.

02 / Warranty and maintenance

Two services, one record per home.

Warranty and maintenance are separate services, but they meet in the same home. A missed maintenance task can void part of a warranty, so the portal keeps both on the same record and shows the link before it becomes a dispute.

In plain words

If the floors are under warranty but the roof drains were never cleaned, and a clogged drain leaks onto the floor, that damage isn’t a warranty claim. The portal shows the homeowner which maintenance protects which coverage, reminds them before it’s due, and gives AB’s team the history when a claim comes in.

example / one home / tap a task

Maintenance plan

Warranty coverage

Interior floors and ceilingsWater damage from the roof
Covered
Deck structureRot and surface failure
Covered
HVAC systemEquipment and installation
Covered
Tap a maintenance task to mark it as missed and see which coverage it puts at risk.

Example rules. The real links between maintenance and coverage come from AB’s warranty document and maintenance guide, approved by AB before go-live. The system flags the risk; a person on AB’s team always makes the coverage decision.

03 / Roadmap

Four steps, each one in use.

Every step ends with something homeowners and AB’s team use every day. Each one is paid for and proven before the next starts, and AB can change the order of steps 2 to 4 after the pilot.

1

Core and native apps

US$28,000

The shared platform with the full warranty service and an estate management pilot, published as AB’s own app on the App Store and Google Play. AB’s team works from the web workspace.

  • Warranty setup, service desk and field visits
  • Estate management: catalog, tiers, one-off services
  • Scheduling, SMS links, response targets
  • Dashboards for AB
  • A. Native apps with push notifications

Homeowners getAB’s own app with their homes, coverage, cases, visits and services, and alerts on their phone.

2

Field release

US$6,000

Offline mode for the field team, so visits at homes with poor reception are recorded on the spot and sync on their own.

  • B. Offline field mode

Homeowners getVisits confirmed on the spot, even with no signal.

3

Revenue release

US$10,000

Homeowners pay and subscribe inside the app, and AB’s marketing team turns one-off services into monthly plans.

  • C. Payments and subscriptions
  • D. Marketing and upsell

Homeowners getCard on file, plans and add-ons, timely offers.

4

Assistance

US$5,300

Answers at any hour: AI that reads each home’s own documents, and a screen for a 24/7 concierge service to log requests.

  • E. AI assistance
  • F. Concierge intake

Homeowners getHelp at 2 a.m., by app or by phone.

Indicative calendar.

weeks from kickoff, confirmed at the technical definition
roadmap / indicative weeks
Step
1234567891011121314151617181920
Technical definitionChecklists and a first model to test
1. Core buildVersions with same-day feedback
1. PilotWarranty and estate management, real homes
A. Native appsBuilt with the core, live at release
B. Offline field modeCapture with no signal
C. Payments and subscriptionsStripe in the app
D. Marketing and upsellCampaigns and offers
E. AI assistanceThree defined uses
F. Concierge intake24/7 request screen
The warranty and estate management pilots run together from week 9, in the native app.The pace assumes AB’s feedback the same day a version arrives.Rows follow the add-ons selected in the investment builder below.

04 / Investment

Build your plan, step by step.

The recommended Phase 1 is the core plus native apps, and the rest stays off until AB is ready. Switch the add-ons on and off to see the total and the monthly costs that come with them. Add-ons that depend on another one switch it on for you.

CorePlatform, warranty service, estate management pilot, scheduling, SMS, dashboards.Always included US$20,000
your plan
Project totalUS$28,000

Recommended Phase 1: core and native apps. Paid in monthly installments during the build.

    Monthly costs that come with this plan

    Fixed prices, by deliverable. Each step is priced for what it delivers: the user stories in Part 2. A new capability that comes up along the way goes to a later step and is quoted before we start it; fixing anything that doesn’t work as agreed is never counted as a change.

    05 / What’s included

    Every step, the same way of working.

    The price of each step covers building it, proving it with real data and supporting it after release. If the budget needs adjusting, we move features to a later step rather than cut testing, the pilot or support.

    D

    Technical definition

    A one-page checklist per app (screens, rules, emails, reports, permissions) and the user stories in Part 2, approved by AB. Every version is checked against them.

    V

    Up to five versions per app

    Each version is reviewed in a weekly session with AB and the changes go into the next one. Fixing anything that doesn’t match the checklist never uses a version.

    C

    A change log

    Every request from a session is logged with its decision: covered, swapped for a story of similar size, moved to a later step, or quoted apart.

    P

    Pilot with real homes

    Four weeks with homes AB selects, real warranty claims and real estate management requests, before the release.

    T

    Training and 60 days of fixes

    Training for AB’s team and supervisors, and bug fixes for 60 days after each release. Support after that runs within AB’s retainer.

    O

    AB owns it

    Code, data, AWS account, app store accounts and Stripe account are in AB’s name, with documentation a developer can work from.

    06 / Monthly costs

    Paid to each provider, no markup.

    Running costs stay around US$100 to US$200 a month for hosting and database, billed by each provider directly to AB.

    ItemCostStarts with
    Hosting, database and file storageAbout US$100 to US$200 a month on AB’s AWS, measured during the pilotPhase 1
    SMSWithin AB’s RingCentral plan; sending by API needs RingCentral’s carrier registration, which Mike starts with themPhase 1
    Card processingStripe’s fee per transactionPhase 1 payment links, then add-on C
    App store accountsApple US$99 a year, Google Play US$25 onceAdd-on A
    AI usageBilled by use on an account in AB’s name; the monthly figure is shared before releaseAdd-on E
    Support after 60 daysWithin AB’s existing retainerPhase 1

    07 / Next steps

    What we need to start.

    With Phase 1 approved, the technical definition and the first version on AB’s AWS start the same week. The order of the add-ons can wait until after the pilot.

    Decisions for AB.

    • Approve Phase 1, the core and native apps, for US$28,000.
    • Confirm Postgres as the database on AB’s AWS (Part 2, decisions).
    • Pick the pilot homes for warranty and for estate management.
    • Choose the order of steps 2 to 4, now or after the pilot.

    Materials from AB.

    • The warranty document and the maintenance guide.
    • Estate management service list, tiers, à la carte prices and current workflow.
    • A spreadsheet of past homes and the stage each one is at.
    • Approval rules, including who approves when Mike is away.
    • Business hours, holidays and what AB considers an emergency.
    • Users by role, and access to AWS, RingCentral’s API and a Stripe account in AB’s name.
    Part 2

    The technical scope, documented.

    How the platform is built so each step plugs in without rework, which data each app touches, the workflows, and the user stories every version is checked against.

    08 / Architecture

    One backend, one app codebase.

    Everything goes through one API and one database from day one. The homeowner and field app is written once and runs in the browser in Phase 1; add-on A publishes that same code to the app stores.

    In plain words

    Think of one kitchen with several service windows. The homeowner app, the field app and AB’s workspace are windows; the kitchen and its pantry are shared. Opening a new window, such as the App Store app or the concierge screen, doesn’t mean building a new kitchen.

    architecture / overview
    People
    HomeownersAB-built homes and estate management clients
    Field staffSupervisors and technicians
    AB teamWarranty, coordinators, management, marketing
    Concierge agentsExternal 24/7 call centerF
    Apps
    Homeowner and field appExpo (React Native). Browser and home screen in Phase 1; App Store and Google Play with A; offline with BPhase 1
    AB workspaceReact web app: coverage setup, service desk, scheduling, catalog, dashboardsPhase 1
    Concierge screenRequest intake for the call centerF
    One API
    Portal serviceNode.js (NestJS) on managed AWS containers. Modules: homes, warranty, maintenance, cases, visits, scheduling, catalog, messages, dashboards; later payments, campaigns, AIPhase 1
    Data
    PostgresManaged on AB’s AWS, automatic backups, point-in-time recoveryPhase 1
    File storage (S3)Photos, documents, closeout records; the database keeps only the linkPhase 1
    Phone storageEncrypted local copy of the field team’s visits for offline workB
    Connected services
    AWS CognitoLogin and sessionsPhase 1
    RingCentralSMS with linksPhase 1
    mondayConnected during the transitionPhase 1
    StripePayment links, then cards and subscriptionsPhase 1 C
    Push notificationsApple and Google, through ExpoA
    AI modelAccount in AB’s nameE
    Red border: the core built in Phase 1.Dashed border: added later.Tags show the step that adds each piece.

    Why this doesn’t need rework.

    The app is written once

    Expo builds the same screens for the browser, iPhone and Android. Going native in add-on A means publishing, push notifications and polish, not new screens.

    The API comes first

    Every screen talks to the same API. A new interface, such as the concierge screen or the dialer, reads and writes the same records without touching the others.

    Proven services, not custom ones

    Login, SMS, payments, subscriptions and push run on established providers. We build AB’s workflows; we don’t rebuild billing engines.

    09 / Data

    Which app touches which data.

    All apps share one database. Tap an app to see what it writes and what it only reads; each role then sees only the homes and records its permissions allow.

    AB team, on the web

    One app, by role

    ONE SHARED DATABASE / POSTGRES

    Homes and ownersProperties, household, AB-built or notReadsWrites
    Warranty coverageItems by trade and periodReadsWrites
    Maintenance plansTasks, due dates, linked coverageReadsWrites
    CasesRequests, decisions, approvalsReadsWrites
    Visits and scheduleDates, crews, verificationReadsWrites
    Photos and documentsLinks to file storageReadsWrites
    Service catalogServices, tiers, pricesReadsWrites
    Plans and paymentsSubscriptions, one-off ordersReadsWrites
    MessagesIn-case chat, SMS, email, pushReadsWrites
    CampaignsSegments and offersReadsWrites
    Users and rolesPermissions by home and roleReadsWrites
    Audit historyWho did what and whenReadsWrites

    Hover over or tap an app to see the data it reads and writes. A homeowner only ever sees their own homes.

    10 / Workflows

    Two journeys, one platform.

    The warranty journey follows the business case step by step. The estate management journey turns a one-off service into a recurring plan.

    Warranty request.

    Phase 1
    workflows / warranty request
    flowchart LR
      A["Homeowner opens a request
    with photos"] --> B["AB reviews against
    coverage and maintenance"]
      B -- "Covered" --> D["Visit booked from
    suggested dates, SMS sent"]
      B -- "Not covered" --> C["Paid service offered
    with payment link"]
      C -- "Accepted" --> D
      D --> E["Field visit
    notes and photos"]
      E --> F["Homeowner confirms
    the visit with QR"]
      F --> G{"Work
    finished?"}
      G -- "No" --> D
      G -- "Yes" --> H["Homeowner approves
    closure and rates"]
      H --> I["Case closed with its
    history, feeds dashboards"]
      classDef ho fill:#162042,stroke:#5d80ff,color:#ffffff
      classDef ab fill:#3a0f1c,stroke:#ff2d55,color:#ffffff
      classDef fi fill:#33200d,stroke:#ff8a24,color:#ffffff
      classDef dec fill:#2e2410,stroke:#e6a830,color:#ffffff,stroke-width:2px
      class A,F,H ho
      class B,C,I ab
      class D,E fi
      class G dec
    Blue: homeowner.Red: AB team.Orange: field and scheduling.Response targets by urgency are measured at every step.

    Estate management.

    Phase 1 pilot, then C and D
    workflows / estate management
    flowchart LR
      A["Any homeowner
    AB-built or not"] --> B["Browses services
    and tiers"]
      B --> C["Books a one-off service
    e.g. bin cleaning"]
      B --> D["Subscribes to a tier"]
      C --> E["Visit booked
    and completed"]
      E --> F["Offer: subscribe
    monthly and save"]
      F -- "Yes" --> D
      D --> G["Adds à la carte
    services anytime"]
      D --> H["Maintenance plan
    kept up to date"]
      H -. "protects" .-> W["Warranty coverage
    AB-built homes"]
      classDef ho fill:#162042,stroke:#5d80ff,color:#ffffff
      classDef ab fill:#3a0f1c,stroke:#ff2d55,color:#ffffff
      classDef fi fill:#33200d,stroke:#ff8a24,color:#ffffff
      classDef gr fill:#0f2d22,stroke:#34d290,color:#ffffff
      class A,B,C,G ho
      class E fi
      class D,F gr
      class H,W ab
    Phase 1: catalog, tiers, one-off requests, payment links.Add-on C: plans and cards paid in the app.Add-on D: the offer after a one-off service is sent automatically.

    11 / User stories

    What each step must do.

    These stories are the scope. Each version is reviewed against them, and a story is done when AB confirms it works with real data. A new story found during the build goes to a later step or replaces one of similar size.

    #As aI want toSo that
    A1HomeownerPlatformLog in once and see each of my homes as its own projectI don’t need separate accounts
    A2Warranty coordinatorPlatformInvite the homeowner when the warranty startsThey have access from day one
    A3Warranty managerPlatformSet what each role can see and doEach person sees only what applies to them
    C1Warranty coordinatorCoverage and maintenanceSet up a home’s warranty from the trades actually builtCoverage matches the home
    C2Warranty managerCoverage and maintenanceApprove a home’s warranty before it becomes activeNothing is promised by mistake
    C3Warranty coordinatorCoverage and maintenanceKeep each home’s maintenance plan, linked to the coverage it protectsA maintenance issue isn’t handled as a warranty claim
    C4HomeownerCoverage and maintenanceSee what’s covered, until when, and which maintenance keeps it validI know before I call
    S1Warranty coordinatorService deskSee each new request with its urgency and response targetNothing waits unnoticed
    S2Warranty coordinatorService deskRecord a decision and send it for approval when the rules require itDecisions are consistent
    S3Warranty managerService deskSee what waits for my approval, with a backup approverCases don’t stop when I’m away
    S4Warranty coordinatorService deskOffer paid service with a payment link when an item isn’t coveredThe homeowner can still get it fixed
    S5Warranty coordinatorService deskMessage the homeowner inside the caseThe whole conversation stays logged with it
    F1SupervisorField serviceSee my visits for the day on my phoneI know where to go and why
    F2SupervisorField serviceRecord inspection, progress and completion with notes and photosThe evidence stays with the case
    F3SupervisorField serviceShow a QR code the homeowner confirms from their own loginThe visit is verified with time and location
    F4SupervisorField serviceRecord photo evidence when the homeowner isn’t homeThe case can still close, with the manager’s approval
    V1HomeownerSchedulingSay when I want the visit and pick from suggested datesI don’t wait for a call back
    V2HomeownerSchedulingReschedule from the app or the SMS linkA change of plans doesn’t need a phone call
    V3DispatcherSchedulingGet dates suggested by crew availability, area and urgencyUrgent cases go first
    E1HomeownerEstate managementBrowse services, tiers and à la carte optionsI pick only what I need
    E2HomeownerEstate managementRequest a one-off service, such as bin cleaningI can try a service before subscribing
    E3Homeowner of a home AB didn’t buildEstate managementSign up for estate management on its ownI get AB’s services without a warranty
    E4Estate managerEstate managementManage the service catalog, tiers and pricesOffers stay current without a developer
    M1HomeownerCommunicationsGet an SMS with a link to the exact case or visitI see updates without searching
    M2HomeownerCommunicationsGet an email at each step that mattersI know what’s happening without logging in
    D1Warranty managerDashboardsSee open cases, response times and pending approvalsI act on what’s late
    D2AB managementDashboardsSee trends by home, trade and type of issueWe learn where problems come from
    N1HomeownerNative appsDownload AB’s app from the App Store or Google PlayThe portal feels like part of my home
    N2HomeownerNative appsGet push alerts for visits, approvals and maintenance dueI don’t miss what needs me
    O1SupervisorOffline field modeRecord visits, notes, photos and confirmations with no signalNothing is lost at homes with poor reception
    O2SupervisorOffline field modeSee what is still waiting to syncI know my work reached the office
    P1HomeownerPayments and subscriptionsSave a card and pay in the appPaying takes one tap
    P2HomeownerPayments and subscriptionsSubscribe to a monthly or annual plan and add services anytimeMy home is looked after without reminders
    P3FinancePayments and subscriptionsSee every payment and subscription matched to its homeCollections reconcile without spreadsheets
    K1MarketingMarketing and upsellBuild segments from portal data: services bought, plan, areaEach offer reaches the right homes
    K2MarketingMarketing and upsellSchedule seasonal campaigns by push and SMSHomeowners hear from us before the rains
    K3MarketingMarketing and upsellOffer the monthly plan with a discount after a one-off serviceOne-time buyers become subscribers
    I1Warranty managerAI assistanceTurn the warranty document into items by trade, approved before go-liveCoverage is data we trust
    I2Warranty coordinatorAI assistanceSee the AI’s first review with the warranty section it relies onI decide faster, with the source in front of me
    I3HomeownerAI assistanceAsk in plain words and get an answer from my home’s documents, with its sourceI get help at any hour
    Q1Concierge agentConcierge intakeLog a homeowner’s call as a request in AB’s system, 24/7Urgent calls reach the team in the morning
    Q2Warranty coordinatorConcierge intakeSee concierge requests in the service desk like any otherThere’s one queue, not two

    12 / Offline

    No signal, no lost visit.

    Add-on B lets the field team work at homes with poor reception. It needs the native app from add-on A, because iPhone browsers don’t keep data reliably without a connection.

    In plain words

    The app keeps its own notebook inside the phone. It always writes there first, so it never waits for a signal. When the phone is back online, it copies the notebook to AB’s system and brings back what changed. Field records are only ever added, never edited by two people at once, so nothing gets overwritten.

    1

    Read locally

    The day’s visits and their homes are on the phone, with the time they were last updated.

    2

    Write locally

    Notes, photos and confirmations are saved on the phone and queued.

    3

    Sync on its own

    When a stable connection returns, the queue is sent and photos upload in the background.

    4

    Confirm

    Each record is marked as synced, and the supervisor sees how many items are still pending.

    What works without signal.

    ActionOfflineHow
    See today’s visits and homesYesLast synced data, with its update time
    Record inspection, progress and completionYesSaved on the phone and sent later
    Take and attach photosYesCompressed and uploaded when signal returns
    Homeowner confirms the visitYesSignature on the supervisor’s phone, with time and location, synced later; QR confirmation when there is signal
    Change a coverage decision or a priceNoOffice decisions stay online, in the AB workspace
    Pay for a serviceNoPayments need a connection

    Before add-on B. In Phase 1 the web app needs a connection to submit. If a home has no reception, the supervisor records the visit once back in coverage, and the homeowner confirms from their own login.

    13 / Decisions

    What we chose, and why.

    The red column is the recommendation; the plan and the prices assume it. The first decision is the one that removes rework.

    D-01

    How we build the homeowner and field app

    Start in the browser now and reach the app stores later, without writing the screens twice.

    CriterionWeb app now, native rebuild laterOne Expo codebaseFlutter app
    Rework to go nativeHighScreens rebuilt for the storesNoneSame code, publishedNone
    Works in the browser in Phase 1YesYesLimitedHeavy to load on the web
    Offline for the field teamWeak on iPhoneStrongWith the native buildStrong
    One language across the systemYesYes, TypeScriptNoDart for the app, TypeScript elsewhere
    Cost over the full roadmapLow now, high laterLowestMedium

    The other decisions.

    DecisionWe recommendInstead ofWhy
    D-02 BackendOne service with modulesMicroservices on KubernetesFits AB’s volume at a fraction of the build and running cost; a module can be split out later if volume calls for it.
    D-03 DatabasePostgres on AB’s AWSMongoDBCoverage, maintenance plans, subscriptions and payments are related records that must stay consistent.
    D-04 HostingManaged AWS containersSelf-run Kubernetes clusterAutomatic restarts, backups and zero-downtime releases without a cluster to operate.
    D-05 PaymentsStripe, payment links then BillingA custom billing engineCards, plans, renewals and receipts are already solved and secure.
    D-06 Offline syncSync library, field records only addedA custom sync engine with conflict reviewField records never clash, so a proven queue covers it.
    D-07 LoginAWS CognitoAn in-house login serviceSecure sessions and password recovery, low cost at AB’s number of homeowners.
    D-08 SMSRingCentralA second SMS providerAB is moving its phones to RingCentral; one provider, one number.

    14 / Security

    Everyone sees only their own.

    Homeowners use the portal for up to ten years. Permissions, backups and history are built in from the first version, not added at the end.

    R

    Roles and homes

    Access by client, home, stage and role, checked on every screen, email, SMS and AI answer. AB approves the permission matrix before the build.

    H

    Audit history

    Approvals, decisions, visits and messages are logged with who, what and when, and stay with the case.

    E

    Encryption

    Encrypted connections everywhere, encrypted database and files, and an encrypted copy on the phone for offline work.

    B

    Backups

    Automatic database backups with recovery to any point in the last days, and versioned file storage.

    D

    Documents

    Only documents AB marks as client-facing appear in the portal; internal working files never do.

    P

    Payments

    Card data stays with Stripe; the portal never stores card numbers.

    15 / Out of scope

    Not in this roadmap, said up front.

    Each of these can be planned and quoted on the same platform when AB is ready.

    ItemWhere it stands
    Call outreach app (dialer)Separate, already approved project; shares the portal’s login and RingCentral connection
    Preconstruction and construction stagesLater release, with Autodesk as the source for schedules and reports
    Design book feedback formsLater release, feedback per design item
    Construction financialsPayment schedules, balances and change orders stay out of the portal for now
    Replacing monday as CRMmonday stays connected during the transition; migration planned separately
    The 24/7 call center service itselfContracted by AB; we recommend providers and build the intake screen in add-on F
    Accounting and tax filingStays in AB’s current tools; Stripe exports feed them

    16 / Glossary

    The technical words, in plain English.

    API
    The service window every app uses to ask for and save information.
    Installable web app
    An app opened from the browser that can be added to the phone’s home screen, with no store download.
    Native app
    An app downloaded from the App Store or Google Play, with push notifications and offline storage.
    Expo (React Native)
    The tool that builds one app for the browser, iPhone and Android from the same code.
    Push notification
    An alert on the phone’s lock screen, sent by the app even when it’s closed.
    Offline mode
    The app saves work on the phone and sends it when the signal returns.
    Postgres
    The database where all of the portal’s records live, with automatic backups.
    S3 file storage
    Amazon’s store for photos and documents; the database keeps only where each file is.
    Stripe
    The payment provider for links, cards, subscriptions and receipts.
    Response target (SLA)
    The time AB commits to respond and repair, by urgency, measured on every case.
    Audit history
    The log of who did what and when, kept with each record.
    Pilot
    Four weeks of real use with selected homes before the release.