Every site, tenant, and broker relationship in one connected HubSpot
Today, acquisition and leasing work is split across a lightly used HubSpot instance, a Dropbox of documents, and a different tracking spreadsheet per person — nothing connects. This project rebuilds the Sales Professional portal around how the business actually works: sites, tenants, lease opportunities, and the brokers who originate them, all linked, with the spreadsheets retired for good.
One source of truth
Every site, tenant, lease opportunity, and broker lives in HubSpot and links to the others. The person-by-person spreadsheets are standardized, imported, and retired.
Relationship visibility
Click into a site and see every interested tenant with its stage. Click into a tenant and see every site it is pursuing. Click into a broker and see everything they originated.
Leadership reporting
Portfolio dashboards show pipeline health, stage-by-stage progress, and broker attribution, so reporting up to leadership no longer means assembling spreadsheets by hand.
Current State to Future State
Legacy Investing runs on three disconnected buckets today. The future state consolidates the tracking work into one rebuilt HubSpot portal, keeps what works, and retires what does not.
HubSpot + spreadsheets + Dropbox
A lightly used Sales Professional portal built informally over two and a half years, leasing tracked in a different spreadsheet per person, and acquisition documents in Dropbox. No shared picture of which tenants are interested in which sites, at which stage, or who brought the relationship in.
One rebuilt Sales Hub portal
Sites, tenants, lease opportunities, and brokers modeled as connected records in HubSpot, one lease-tenant pipeline with clear stages, and dashboards for the Acquisitions team, the Leasing team, and leadership. Dropbox stays for documents; tracking happens in one place.
How each system is treated in the move:
HubSpot Sales Professional
The existing portal is optimized rather than replaced: a new data model, record layouts, permissions, pipeline, and dashboards, with outdated properties archived.
Leasing Spreadsheets
Standardized, imported into HubSpot, and retired. Historical tracking data carries forward into the new data model.
Dropbox
Stays as-is. The managing partners rely on it, and document storage is not part of this scope. Tracking data moves to HubSpot; files do not.
What We're Migrating
The leasing team's tracking spreadsheets are the source data. Each person keeps their own format today, so Aptitude 8 consolidates, deduplicates, and reshapes that data against a Legacy Investing approved import template before anything is loaded.
- Roughly 4 analysts, each tracking in their own spreadsheet format — no shared template exists today
- On the order of 100 lease-tenant opportunities at most coming out of the spreadsheets
- Prospecting and relationship-building records run higher; the activity-date cutoff for what's worth importing is decided in requirements
- Exact counts are confirmed before contract wherever possible; materially more records or more complexity than assumed results in a change order
| What's Tracked Today | Where It Lives in HubSpot |
|---|---|
| Acquisition sites and targets | Listings records, with power capacity, acquisition status, and sourcing attribution |
| Prospective and active tenants | Company records, with the individual people tracked as Contacts underneath |
| Tenant-site pursuits and their stages | Deals in the lease-tenant pipeline, one per tenant-site pairing, each tracking its own stage |
| Broker relationships | Contact records, optionally paired with a Company for the brokerage, linked to the sites and tenants they originated |
A single one-time import. Dropbox documents are not migrated, and no recurring sync is in scope. Legacy Investing signs off on the import template before Aptitude 8 begins data manipulation.
Key Assumptions, Risks, and Dependencies
The scope and timeline hold if the items below hold. None of them are unusual; all of them are real.
Record volumes unconfirmed
No one has counted the sites, tenants, brokers, or historical deals yet. Data preparation is sized to the working volume assumption above — dozens, not hundreds, of active pursuits. Materially more records or complexity results in a change order.
Listings object fit
Sites are planned on HubSpot's native Listings object, included in the current plan. If it proves too limited and a fully custom object is needed, that requires a Sales Enterprise upgrade, a licensing cost decision that gets made during solution design, not discovered mid-build.
Import template signoff
Aptitude 8 does not begin manipulating spreadsheet data until Legacy Investing signs off on the import template. The signoff gate protects the data; it also sits on the critical path.
Portal access and spreadsheets
Partner access to the HubSpot instance and at least 2 representative leasing spreadsheets are provided at kickoff, so the portal audit and data quality assessment start on time.
No compliance requirements
We assume no compliance or data-sensitivity requirements apply. If a real requirement surfaces — for example deal-level access restrictions — it would shape the permissions design and be handled as a change.
Aptitude 8 is a Time & Materials agency; budget is tracked transparently and change orders require approval. Assumptions are based on information gathered during the sales evaluation and are subject to refinement during the project.
Your Scenarios, Running on the Proposed Data Model
Nothing on this tab is hypothetical. Each scenario below was described by the Legacy Investing team on the discovery calls, in your own words, and each was tested against the proposed data model before this scope was priced. The first two were walked through together as live mockups on the August 11 working session; the dashboard view was shown on the same call. If the model handles these three, it handles the way Legacy Investing actually works.
The connecting piece is the Lease Opportunity: every tenant-site pursuit is its own record, linking one site to one tenant and carrying its own stage. Everything below falls out of that one decision.
Finding Tenants for a Site
- Someone on the leasing team opens the site record for a property the acquisition team sourced.
- Right on that record, they see candidate tenants — companies whose power requirement fits this site's capacity, including ones already in conversation and ones not yet approached.
- From there, they pick a tenant and start a lease opportunity connecting that tenant to this site, at whatever stage makes sense.
| Tenant | Why They Fit | Already in Process? | |
|---|---|---|---|
| Hyperscale Co. | Needs 50 MW — matches this site's capacity | — | Start Lease Opportunity |
| DataCore Partners | Needs 20 MW — within capacity | Letter of Intent | View Lease Opportunity |
| CloudEdge Inc. | Needs 80 MW — above this site's capacity | — | Start Lease Opportunity |
“Nesting Dolls” — One Tenant, Many Sites, Different Stages
| Site | Stage | Last Activity |
|---|---|---|
| 123 Main St | Letter of Intent | 3 days ago |
| 456 Powerline Rd | Traded Paper | 1 week ago |
| 789 Grid Ave | Interested | Today |
Dashboards for All of It
- Leadership opens a portfolio dashboard — every active pursuit across every site and tenant, without opening a single record.
- They slice the same data the way the acquisition team described: all targets by status, only what's under LOI, only what's owned.
- The same records re-slice by broker — who originated what, and who's earning the fees they're paid.
| Tenant | Site | Stage | Broker |
|---|---|---|---|
| DataCore Partners | 123 Main St | Letter of Intent | Broker J.R. |
| DataCore Partners | 456 Powerline Rd | Traded Paper | Broker J.R. |
| DataCore Partners | 789 Grid Ave | Interested | — |
| Hyperscale Co. | 123 Main St | Interested | — |
| CloudEdge Inc. | 901 Substation Way | Executed | Broker T.N. |
| Broker | Sites Sourced | Tenants Introduced | Active Opportunities | Executed |
|---|---|---|---|---|
| Broker J.R. | 3 | 2 | 2 | 1 |
| Broker T.N. | 1 | 1 | — | 1 |
One structural note: the association pattern proven above holds whether Site ultimately lives on HubSpot's native Listings object or a fully custom object. The Listings-fit decision flagged under Key Considerations changes licensing, not this model. Mockups are illustrative of behavior, not final screen designs; broker names are anonymized.
Mobilization
Contracted6hHigh7h
Aligning project teams, confirming objectives, setting up governance, and conducting a structured kickoff call with the Acquisitions and Leasing teams to get the HubSpot rebuild started.
Mobilization
Mobilization
Contracted6hHigh7h
A structured kickoff that aligns the Acquisitions and Leasing teams, and the project sponsor, on roles, access, and next steps before work begins.
Requirements
Contracted21hHigh23h
Reviewing and validating the site, tenant, lease-opportunity, and broker relationship model and the leasing spreadsheet data to be imported, so both are clearly understood before solution design begins.
Requirements
Acquisitions & Leasing Requirements
Contracted15hHigh17h
A validated picture of how sites, tenants, lease opportunities, and brokers connect today, plus the record volumes and open data-model questions needed before design starts. Limited to the Acquisitions and Leasing teams — no marketing, service, or reporting processes outside those teams are included.
Data Import Requirements Clarification Needed
Contracted6hHigh6h
An assessment of the leasing-tracking spreadsheets to be imported, covering format, completeness, and what's worth carrying forward. Covers spreadsheet data only — Dropbox documents themselves are not migrated.
Solution Design
Contracted20hHigh23h
Defining how the data model, single lease-tenant pipeline, and leadership dashboards will be built, including resolving the Listings-vs-custom-object decision, and obtaining sign-off before implementation begins.
Solution Design
Acquisitions & Leasing Solutions Design
Contracted8hHigh10h
A finalized data model, pipeline design, users & permissions structure, and reporting plan, signed off before any building begins. Includes resolving the Listings-vs-custom-object decision and the co-brokerage, stage-history, and cold-pairing open items from the ERD review.
Data Import Solutions Design Clarification Needed
Contracted8hHigh9h
A signed-off import template mapping spreadsheet data to HubSpot properties, plus a defined sequencing and deduplication plan for the historical leasing data. Legacy Investing's signoff on the template is required before data manipulation begins.
Solution Validation
Contracted4hHigh4h
Formal review and sign-off of the finalized solution design — data model, pipeline structure, and reporting approach — with Legacy Investing before implementation begins.
Implementation
Contracted61hHigh67h
Implementing the HubSpot data model, record layouts, permissions, lease-tenant pipeline, and dashboards, and preparing and loading the historical leasing data, through configuration and data manipulation.
Implementation
HubSpot Configuration
Contracted26hHigh28h
The Site, Tenant, Lease Opportunity, and Broker data model built in HubSpot, with record layouts, permissions, and legacy property cleanup completed. Supports the many-to-many relationships and cross-record navigation the Acquisitions and Leasing teams described.
Sales Hub Implementation
Contracted19hHigh20h
A single lease-tenant pipeline with supporting automations, plus portfolio and team-level dashboards covering pipeline health and broker attribution. Includes the training and reference materials the Acquisitions and Leasing teams need to adopt it.
Data Import Clarification Needed
Contracted16hHigh19h
Legacy Investing's historical leasing and acquisition data, cleaned and standardized from each person's spreadsheet format, loaded into the rebuilt HubSpot instance across four target objects: Listings (Sites), Companies (Tenants), Deals (Lease Opportunities), and Contacts (Brokers). Covers a single, one-time import — not a recurring or phased process.
Testing
Contracted19hHigh21h
Validating the data model, pipeline, dashboards, and imported leasing data against what the Acquisitions and Leasing teams described during discovery.
Testing
HubSpot Configuration
Contracted8hHigh8h
The Site, Tenant, Lease Opportunity, and Broker data model built in HubSpot, with record layouts, permissions, and legacy property cleanup completed. Supports the many-to-many relationships and cross-record navigation the Acquisitions and Leasing teams described.
Sales Hub Implementation
Contracted8hHigh10h
A single lease-tenant pipeline with supporting automations, plus portfolio and team-level dashboards covering pipeline health and broker attribution. Includes the training and reference materials the Acquisitions and Leasing teams need to adopt it.
Data Import
Contracted3hHigh3h
Legacy Investing's historical leasing and acquisition data, cleaned and standardized from each person's spreadsheet format, loaded into the rebuilt HubSpot instance across four target objects: Listings (Sites), Companies (Tenants), Deals (Lease Opportunities), and Contacts (Brokers). Covers a single, one-time import — not a recurring or phased process.
Training
Contracted14hHigh16h
Equipping the Acquisitions and Leasing teams with the knowledge and confidence to adopt the rebuilt HubSpot instance, with a deliberate focus on adoption given past frustration with the prior setup.
Training
Sales Hub Implementation
Contracted14hHigh16h
A single lease-tenant pipeline with supporting automations, plus portfolio and team-level dashboards covering pipeline health and broker attribution. Includes the training and reference materials the Acquisitions and Leasing teams need to adopt it.
Deployment
Contracted6hHigh6h
Cutting the Acquisitions and Leasing teams over to the rebuilt portal — configured directly in production, with no sandbox required — and supporting the transition to live use.
Deployment
Launch
Contracted6hHigh6h
The rebuilt configuration switched into live use through a coordinated cutover — the portal is optimized directly in production — with validation that everything works correctly before the Acquisitions and Leasing teams rely on it day to day.
Hypercare
Contracted13hHigh14h
Providing concentrated support in the two weeks immediately following launch to monitor the rebuilt HubSpot instance and resolve any issues before transitioning to Managed Services.
Hypercare
Hypercare
Contracted13hHigh14h
Two weeks of monitoring and defect resolution immediately after launch so early issues are caught and fixed before Legacy Investing transitions to ongoing Managed Services support.
Project Management
Contracted48hHigh53h
Maintaining project health through status meetings, timeline tracking, budget visibility, and proactive communication with Legacy Investing given the urgency expressed around this rebuild.
Project Management
Project Management
Contracted48hHigh53h
Ongoing project coordination, status communication, and budget/timeline tracking across the engagement.
Post-Launch Support
Following Hypercare, A8 recommends ongoing retainer-style support delivered by our Managed Services team — reporting, training, iterations, and ongoing optimization as the Acquisitions and Leasing teams settle into the rebuilt portal.
Rate $260/hr. Contracted hours are a variable ceiling — billed against actuals up to the contracted amount per workstream; High is the upper bound of the estimate band. Post-Launch Support is a recommended, separately contracted retainer at $260/hr that begins after Hypercare.
Project Timeline
An illustrative plan anchored to a Tuesday, September 1, 2026 kickoff; actual dates set at contract signature.
- Requirements and solution design run through early October; the build runs through early November
- Testing and training land in mid to late November; go-live is Friday, December 4
- Two weeks of hypercare through December 18, then a month of Managed Services through mid-January
- Roughly a 13-week plan — it holds if Legacy Investing invests early in the requirements window, and compresses toward 11 to 12 weeks at two workshops per week
Levers if the Timeline Compresses
Legacy Investing has asked for speed. Some of this schedule can move faster; the split is largely about who owns the pace.
We Can Speed Up
- Workshop cadence: two requirements workshops per week instead of one compresses the discovery window by roughly two weeks. This is the single biggest lever, and it is in Legacy Investing's hands.
- Build parallelization: once the design is signed off, the data model, pipeline, and dashboard work can overlap rather than run in sequence.
- Training scheduling: recorded, role-based sessions can land alongside client testing rather than strictly after it.
We Can't Speed Up
- Client signoff gates: solution validation and the import template signoff are hard gates. Skipping them is how the last HubSpot build ended up where it is.
- Client testing: the Acquisitions and Leasing testers need real time in the system before go-live; compressing the testing window trades launch quality for days.
- Data preparation quality: standardizing a different spreadsheet per person takes the time it takes. Rushing it recreates today's mess inside the new system.