Every site, tenant, and broker relationship in one connected HubSpot
Today, Legacy Investing's acquisition and leasing work is split across a HubSpot instance built informally as the team was smaller, a Dropbox of acquisition documents, and a different tracking spreadsheet for every person on the leasing team. Nothing connects, and the people who need answers spend their time hunting for them. This project rebuilds the Sales Professional portal around how the business actually works: acquisition sites, prospective tenants, lease opportunities, and the brokers who originate them, all linked so anyone can trace a relationship from any starting point, 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 standardizes, deduplicates, and reshapes that data against a Legacy Investing approved import template before anything is loaded. Record counts are confirmed during the requirements phase; the mapping below shows where each kind of data lands.
| 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.
What This Plan Depends On
The scope and timeline hold if the commitments below hold. None of them are unusual; all of them are real.
The Acquisitions and Leasing teams need to show up early and often in the first month: up to 4 discovery workshops, up to 2 solution design workshops, at least 2 representative leasing spreadsheets handed over before requirements begin, and prompt signoff on the import template. Every week of delay in this window pushes the go-live a week.
Record volumes unconfirmed
No one has counted the sites, tenants, brokers, or historical deals yet. Data preparation is sized to Legacy Investing's own description of dozens, not hundreds, of active pursuits; materially higher volumes get re-scoped in requirements.
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 needed at kickoff for the portal audit and data quality assessment to start on time.
Relationship model edge cases
Co-brokerage handling, stage history needs, and how a cold tenant-site pairing is represented are open questions from the data model review, resolved in the solution design workshops.
Compliance requirements
No compliance or data-sensitivity requirements have been confirmed either way. A real requirement here, for example deal-level access restrictions, would shape the permissions design.
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.
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
Requirements
Contracted23hHigh25h
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 Clarification Needed
Contracted17hHigh19h
Data Import Requirements Clarification Needed
Contracted6hHigh6h
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 Clarification Needed
Contracted12hHigh14h
Data Import Solutions Design Clarification Needed
Contracted8hHigh9h
Implementation
Contracted67hHigh73h
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 Clarification Needed
Contracted26hHigh28h
Sales Hub Implementation
Contracted21hHigh23h
Data Import Clarification Needed
Contracted20hHigh22h
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
Sales Hub Implementation
Contracted8hHigh10h
Data Import
Contracted3hHigh3h
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
Deployment
Contracted9hHigh9h
Moving the rebuilt data model, pipeline, dashboards, and imported leasing data into production and supporting the transition to live use.
Deployment
Launch
Contracted9hHigh9h
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
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
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 late October, testing and training land in early November, and go-live is Friday, November 13, followed by two weeks of hypercare through November 27 and an optional month of Managed Services. This is an 11-week plan on the full scope, and it holds if Legacy Investing invests early in the requirements window. At a cadence of two workshops per week, the same scope can compress toward 9 to 10 weeks.
Requirements to Launch Safely
The November go-live is achievable on the full scope because the schedule front-loads requirements and design. That only works if these commitments hold in the first month.
| Commitment | What it means |
|---|---|
| Workshop availability | Acquisitions and Leasing stakeholders attend up to 4 discovery workshops and up to 2 solution design workshops during September. One workshop per week fits the 11-week plan; two per week compresses it. |
| Spreadsheet handoff | At least 2 representative leasing spreadsheets are provided before requirements begin, so the data quality assessment starts on real files, not descriptions of them. |
| Portal access at kickoff | Partner access to the HubSpot instance is in place for the kickoff, so the portal audit runs in week one. |
| Import template signoff | Legacy Investing reviews and signs off on the field mapping document and the import template promptly. Data manipulation cannot start without the template signoff, and the import sits on the critical path to go-live. |
| Listings decision in design | The Listings-versus-custom-object decision is resolved during solution design, including any plan tier implications, so the build starts on a settled data model. |
A single coordinated cutover
- The approved configuration is promoted to production in one go-live event: data model, record layouts, permissions, the lease-tenant pipeline, automations, and dashboards.
- The standardized historical data is imported once, after test-import validation, and spot-checked in context on the finished record layouts and dashboards.
- The Acquisitions and Leasing teams are trained before go-live, with session recordings kept for onboarding future users.
- Production validation runs immediately after cutover, then two weeks of hypercare monitoring and defect resolution carry the teams through their first weeks in the live system.
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.