The real estate procurement negotiation and transaction management platform that connects buyer agents, listing agents, brokers, sellers, and buyers.
Hire All The Agents (HATA) is a web-based platform that manages the documented procurement negotiation lifecycle in real estate transactions. It provides tools for buyer agents to search listings, request written seller-side procurement terms from listing agents, negotiate terms, electronically sign agreements, schedule property showings, and manage transaction documents — all in one place.
The platform is built as a progressive web app (PWA) that works on desktop and mobile browsers. It supports offline capabilities, push notifications, and can be installed on a phone's home screen for a native-app feel.
HATA serves the real estate industry in the post-NAR settlement era, where buyer-agent payment terms are no longer published on the MLS and seller-side procurement terms must be documented directly between parties. The platform replaces phone calls, emails, and paper forms with a structured digital workflow that creates a legally defensible audit trail for every negotiation.
After the 2024 National Association of Realtors (NAR) settlement, buyer-agent payment terms can no longer be advertised on MLS listings. This created several challenges:
HATA solves these problems by providing a digital platform where seller-side procurement terms can be requested, negotiated, agreed upon, and legally signed — with a full audit trail at every step.
HATA supports 13 distinct user roles, each with a tailored dashboard and role-specific features:
| Role | What They Do on HATA |
|---|---|
| Buyer Agent | Search listings for documented procurement terms, submit offers, negotiate with listing agents, sign agreements, schedule showings, manage buyer clients, and track all transactions through the inbox. |
| Listing Agent | Receive procurement requests from buyer agents, respond with accept/decline/counter, manage their listings, set showing availability, handle guest portal approvals, and forward agreements to sellers when needed. |
| Broker Admin | Manage brokerage-level settings, create and maintain agreement templates, set brokerage branding for emails and documents, and oversee agents within their brokerage. |
| Team Admin | Coordinate a team of agents, manage team-level settings and permissions. |
| Role | What They Do on HATA |
|---|---|
| Seller | Review and sign procurement agreements when the seller is the payer for a Property-Specific Procurement Offer. Access the guest portal without needing an account. Track agreement status. |
| Buyer | View buyer-fee disclosures, BRA-specific Contractual Procurement Credits, and transaction documents related to their purchase. |
| Role | What They Do on HATA |
|---|---|
| Loan Officer | Access the document vault for executed agreements needed for loan processing. |
| Title Company Rep | Access executed documents needed for title work and closing. |
| Insurance Agent | View transaction documents relevant to insurance underwriting. |
| Inspector | Access property and transaction information for inspection scheduling. |
| Appraiser | View property details and transaction documents for appraisal work. |
| Role | What They Do on HATA |
|---|---|
| App Admin | Full platform administration: manage users, roles, system defaults, agreement templates, email templates, branding, signing sessions, and master contacts. |
Users can hold multiple roles simultaneously. A real estate professional who represents both buyers and sellers can have both the Buyer Agent and Listing Agent roles active at the same time, switching between them with a single click.
The Procurement Check page is the starting point for buyer agents. It allows them to review documented, property-specific seller/listing-side procurement status and the governing buyer-representation terms before touring.
HATA includes an AI data extraction engine powered by Google Gemini. Agents can upload MLS documents (PDFs, screenshots, images) and HATA automatically extracts property data — address, price, bedrooms, bathrooms, square footage, lot size, listing agent information, and more. This eliminates manual data entry and works with any MLS format.
The system supports three import methods: drag-and-drop onto the search form, file upload button, and clipboard paste (for screenshots). CSV files from MLS exports are also supported with automatic column mapping.
Agents can forward MLS documents to a dedicated HATA intake email address. The system processes attached documents and imports the extracted listings, which appear in the agent's Procurement Check results the next time they visit the page.
The negotiation system manages a traceable request between a Buyer Brokerage Authorized Representative and the actual authorized payer-side participant. A listing agent may route a request but is not treated as the payer merely because they received it.
| Status | Meaning |
|---|---|
| In Queue | Added to the negotiation queue but not yet sent |
| Submitted | Sent to the listing agent, awaiting their response |
| Read | Listing agent has opened and viewed the request |
| Accepted | An acceptance response was recorded; the agreement is not formed until every required signer completes the same current revision |
| Rejected | The listing agent declined the offer |
| Counter | One party proposed different terms — the other must respond |
| No Reply | No response within the allowed time period |
| Withdrawn | The offer was cancelled before resolution |
HATA never infers the payer from the routing recipient or defaults the payer to a listing brokerage. The requester's traceable proposed-payer choice remains a proposal until an authorized payer-side actor identifies the legal payer, confirms capacity, and assents to exact terms:
The Inbox is the central hub for all conversations in HATA — procurement negotiations, showing requests, and direct messages between agents.
Conversations are automatically sorted into three priority sections:
Opening a conversation shows a full thread view similar to a messaging app:
Agents can start direct conversations with any other agent on the platform by searching for them by name, email, phone, or license number. This enables communication outside of specific transactions.
The inbox updates in real time via WebSocket connections. New messages appear instantly, status changes update automatically, and unread counts refresh without page reloads.
The Showing Scheduler helps buyer agents schedule property tours and listing agents manage showing requests for their listings.
After a showing, buyer agents can rate the property (Loved it, Liked it, Neutral, Concerns) and optionally share feedback with the listing agent.
A mobile-friendly daily view shows all showings as cards with touch-friendly 44px targets. Includes a "Done Here" checkout button that tracks visit duration.
Listing agents can Accept, Decline, or Counter showing requests directly from email notifications — no login required. One-click response buttons in the email.
Listing agents can add occupants (tenants, homeowners) as contacts on their listings. Occupants automatically receive email notifications when showings are scheduled, confirmed, or cancelled — keeping them informed without needing a HATA account.
The system automatically detects when a buyer agent doesn't check in for a confirmed showing, flags potential no-shows, and notifies the listing agent.
HATA includes a complete electronic signature system for creating, sending, signing, and verifying legal documents.
Admins and broker admins manage reusable agreement and email templates. Agreement templates support merge fields (placeholders) that auto-fill with transaction data — property address, agent names, procurement amounts, dates. Broker admins can set brokerage-wide default templates.
A visual editor lets users place fillable fields directly on existing PDF documents. Features include drag-and-drop field placement, multi-select for batch operations, 50-step undo history, and multi-page document support. Fields are color-coded by signer for easy identification.
HATA provides two document management systems: the Document Hub (personal vault) and the Documents page (agreement-specific).
The Documents page shows all procurement agreements and other negotiation-related documents. Features include table, card, and folder views; filtering by scope, type, status, relation, date, and search; and PDF download with full agreement details, signatures, and procurement terms.
Vendor roles (loan officers, title reps, etc.) have read-only access to executed documents from transactions they're involved in. This supports loan processing, title work, and other vendor tasks that require access to signed agreements.
The Guest Portal enables listing agents and sellers to interact with HATA without creating an account. This is critical for adoption — the platform works even when only the buyer agent has an account.
Notification emails link to a transaction-scoped review surface. The user must open the portal and satisfy its current identity, authority, review, and signing gates before a protected action is recorded.
A registered user who already has a valid authenticated session may continue in the authorized app context. An email address or link by itself never creates an authenticated session and never proves transaction authority.
Each guest link contains a unique, hashed token tied to a specific transaction. Tokens are single-use for signing actions, expire after a set period, and are scoped to only the relevant transaction data. PIN verification adds an extra security layer.
After signing, the guest portal walks listing agents through optional steps to deepen engagement:
When the seller is the payer for a Property-Specific Procurement Offer, they receive their own guest portal link. The seller flow includes: reviewing the procurement terms, entering their contact information, confirming the procurement payer arrangement, and e-signing the agreement. Co-seller invitations are supported for properties with multiple owners.
Listing agents manage their property portfolio from the My Listings page. They can add listings manually (entering property details) or import them from MLS documents using HATA's AI extraction engine.
When a listing appears in the system (imported by a buyer agent), the actual listing agent can claim ownership by verifying their real estate license number. The system validates the license against state databases.
For each listing, agents configure showing policies: auto-confirm (buyer agents can book instantly) or confirmation required (listing agent must approve each request). They can also add occupant contacts for automatic showing notifications.
The Property-Specific Procurement Offer (SPPO) composer helps listing agents prepare a property-specific offer from the identified payer. The payer may be the seller or the listing broker acting with the required authority.
Agents maintain a contact database of other professionals they work with. Contact records include name, email, phone, license number, brokerage, and company details. Contacts can be segmented by type (agents, clients, vendors).
Buyer agents manage their buyer clients — the individuals they represent in transactions. Selecting an active client is required before running procurement checks (to comply with buyer-agent agreement requirements). The client switcher in the app header allows quick switching between clients.
App admins have access to the Master Contacts directory — a searchable database of all contacts across the platform, with the ability to verify, merge, and manage contact records.
Platform administrators have a comprehensive dashboard for managing:
Brokerage leaders can manage brokerage-level settings, set default agreement templates for their agents, configure brokerage branding, and manage form templates used by their team.
A developer-focused admin page for managing database schemas, running migration scripts, and monitoring database health. Includes one-click script execution for common database operations.
HATA supports five vendor roles for transaction participants beyond the buyer and listing agents:
| Vendor Role | Dashboard Features |
|---|---|
| Loan Officer | Access executed agreements for loan processing. Document vault with executed procurement agreements. Communication tools for coordinating with agents. |
| Title Company Rep | View transaction documents needed for title searches and closing preparation. Access executed agreements and contact information for all parties. |
| Insurance Agent | Access property details and transaction documents for insurance quoting and underwriting. |
| Inspector | View property information and schedule coordination for home inspections. |
| Appraiser | Access property details, comparable sales data, and transaction documents for appraisal work. |
Each vendor role has its own tailored dashboard, requires a participation agreement before activation, and has scoped access limited to transactions they're assigned to.
HATA never suggests, defaults, or recommends procurement amounts or buyer-representation fee amounts. All amount fields start empty. The platform does not aggregate or publish "average" or "typical" rates. It facilitates direct negotiation between individual parties without influencing pricing.
| Layer | Technology |
|---|---|
| Frontend | React 19, TypeScript, Vite, Tailwind CSS |
| Backend | Supabase (PostgreSQL database, authentication, real-time subscriptions, storage) |
| Serverless Functions | Supabase Edge Functions (Deno runtime) — 32 functions handling email, documents, webhooks, AI processing |
| AI / ML | Google Gemini API for MLS document OCR and data extraction |
| Resend API for transactional email delivery with webhook tracking | |
| Maps | Google Maps integration for tour routing and GPS check-in |
| PWA | Progressive Web App with offline support, push notifications, and installable home screen icon |
| Testing | Playwright for end-to-end tests, Vitest for unit tests |
| Term | Definition |
|---|---|
| Buyer Agent | A licensed real estate agent who represents the buyer in a property transaction. |
| Listing Agent | A licensed real estate agent who represents the seller and manages the property listing. |
| Procurement Fee | Compensation for defined Procurement Services under property-specific seller/listing-side terms. It is separate from any Buyer Representation Fee. |
| Buyer Representation Fee | Compensation for representing a buyer under the governing Buyer Representation Agreement. It is separate from the Procurement Fee. |
| Contractual Procurement Credit | A credit against the Buyer Representation Fee only to the extent required by the governing Buyer Representation Agreement. The rule may vary by agreement. |
| Remaining Buyer-Paid Maximum | The buyer's maximum remaining obligation under the governing Buyer Representation Agreement after applying the Contractual Procurement Credit and any other required credits. If the agreement or credit rules are missing or unclear, the buyer obligation is not yet determined. |
| Procurement Check | HATA's property-specific review of documented seller/listing-side procurement status and governing buyer-representation terms before touring. It does not search for or rank Buyer Representation Fees. |
| Negotiation | The back-and-forth process between a buyer agent and listing agent to agree on procurement terms. |
| Counter Offer | A response to a procurement request that proposes different terms than what was originally offered. |
| Guest Portal | A streamlined interface that allows listing agents and sellers to review and sign agreements without creating an account. |
| Magic Link | A secure, single-use URL sent via email that gives the recipient direct access to a specific transaction without logging in. |
| E-Sign Consent | An explicit agreement by the signer to use electronic signatures, required by law before capturing a digital signature. |
| Participation Agreement | A legal agreement that users must sign before accessing role-specific features on the platform. |
| MLS | Multiple Listing Service — a database used by real estate agents to share property listings and cooperate on sales. |
| NAR Settlement | The 2024 National Association of Realtors legal settlement that changed how buyer-agent payment terms are handled, removing them from MLS listings and requiring direct negotiation. |
| SPPO | Property-Specific Procurement Offer. A property-specific written offer from the identified payer, who may be the seller or the listing broker acting with the required authority. |
| RLS | Row-Level Security — a database feature that ensures users can only access data they are authorized to see. |
| Document Vault | A secure storage area where vendors can access executed documents from transactions they are involved in. |
| Signing PIN | A 4-digit code that signers create to verify their identity in future signing sessions. |
| Showing Policy | A listing-level setting that determines whether showing requests are automatically confirmed or require manual approval from the listing agent. |
| Tour Routing | An optimization feature that arranges multiple property showings in the most efficient driving order. |
| Procuring Cause | The legal concept that the agent who was the primary reason a buyer purchased a property may be entitled to a fee. |