FYC Labs · Website and Yardi integration · Proposal for H.G. Fenton

Mark it once in Yardi.
The site follows.

Your leasing team enters every unit twice today. In 12 weeks they enter it once, in Yardi, and SRMurban.com catches up on its own. Same structure, same map, new engine underneath.

For Matt and the H.G. Fenton team 12 weeks · $13,000 fixed · 10.7.2026
01 · The situation

Every unit gets
entered twice.

Someone on the SRM team marks a unit available in Yardi, sets the price and the terms, then opens WordPress and does it again by hand. It takes about 30 seconds and they're fast at it.

The cost shows up when somebody skips it. A unit that's live in Yardi and dark on the site never gets marketed, and a stale price on a published listing is a fair housing problem rather than a typo.

You're moving the whole portfolio off MRI onto Yardi anyway. The site is the last piece still running on hands, and it's also the piece doing the least commercial work for you today.

What the site runs on today
  • 01
    WordPress, hand-enteredEvery listing typed in twice, once in Yardi and once here
  • 02
    No scheduler worth the nameWP-Cron fires on page visits, so a quiet night skips the run
  • 03
    Near-zero SEO and AEONo metadata, no structured data, no answer-engine presence
  • 04
    No measurement at allNo event tracking, no attribution, nothing to judge the site by
SRM Urban · Website and Yardi02
02 · The investment

One fixed price.
Add what you want.

Fixed price $13,000 Billed half at signature, half at launch.
Hours 93 Design, development, project management, and QA. Every hour is on the scope pages.
Timeline 12 Weeks, kickoff to launch.

The base covers the rebuild, the Yardi integration, and the tracking stack. Your current structure and map browsing carry over, so the hours go into moving the site rather than redrawing it. Yardi credentials are already live, so development starts the week you sign.

Running costs after launch
  • Cloud hostingAbout $20 a month
  • Headless CMS$20 to $50 a month
  • Yardi RentCafe APIIn-house license, already yours
Add-ons on page 10 update these numbers03
03 · What we're building

The site moves.
Yardi does the typing.

01

Rebuilt on Next.js

We keep the structure, the map, and the look your renters already use. Underneath it runs on a modern stack your team can extend without fighting plugins or waiting on a release.

02

Yardi as the only entry point

Availability, pricing, lease terms, photos, and floor plans pull from RentCafe on a schedule. Your team marks a unit in Yardi and the website catches up on its own.

03

Search that reads real inventory

Find Your Pad filters on bedrooms, price, neighborhood, and pets against live data. Map and list stay in sync, and a failed refresh shows the last good data instead of nothing.

04

Unit pages that build themselves

One page per available unit, created and retired by what Yardi says. Street and neighborhood lead, the way SRM actually rents, with apply links hitting the right RentCafe record.

05

Tracking and retargeting

Tag Manager, GA4, and Customer.io wired to real events. Google and Meta pixels installed, so a renter who looked at a unit twice can see it again in their feed.

06

Content your team owns

Neighborhood copy, FAQ entries, and page metadata move into a content system your marketing team edits directly, so there is no developer in the loop for a copy change or a new FAQ.

SRM Urban · Website and Yardi04
04 · What goes away

Four risks.
Three close.

Each risk the current WordPress setup carries, and what happens to it on the new stack.

The riskOn WordPress todayOn Next.js and a real scheduler
Refresh that missesWP-Cron fires on page visits, not on a clock. A quiet night means the 8 hour Yardi token expires and the first visitor gets an error.Closed
A real scheduler refreshes the token inside the window whether anyone visits or not.
Overlapping callsWordPress has no job lock, so two visitors can fire the same refresh twice. Yardi bans overlapping calls to the same method by name.Closed
A queue with locking runs one job at a time and counts its own calls against the daily ceiling.
Credentials in the databaseTokens and the vendor password sit in wp_options, readable by every plugin on the site and every admin user.Closed
Credentials live outside the site, in the integration service, with nothing on the front end holding a secret.
A wrong price in YardiA typo in Yardi and a typo on the site are two separate mistakes, and each one can hide the other.Still a risk
One source of truth means a wrong price publishes faster and more visibly. Fewer mistakes, less time to catch one.

We would rather tell you the fourth one gets sharper than pretend a rebuild fixes data entry.

SRM Urban · Website and Yardi05
From Matt, on the scoping call

"I don't want more work and more complexity. I want more customers."

Matt PutmanTechnology, H.G. Fenton Company
SRM Urban · Website and Yardi06
05 · The timeline

12 weeks,
around your cutover.

W1W2W3W4W5W6W7W8W9W10W11W12
Data contract and Yardi auth
W1 to W2
Site build
W2 to W5
Integration against live data
W3 to W6
SRM properties in Yardi
W7 to W9
Tracking, QA, your review
W9 to W11
Launch and handoff
W12

Yardi credentials came through on September 25, so we build against your live institutional properties from week 3 instead of waiting on a sandbox. SRM's own data lands after the October cutover, which is what week 7 is for.

SRM Urban · Website and Yardi07
06 · The scope · Part 01 of 02

What your renters see.

Open any line to see what's included.

#ItemTypeDesignBuild
  • Map pins draw from cached Yardi data, not manual entry
  • Featured units surface by availability date with no curation step
  • Neighborhood tiles route into the shared content template
  • Hero video and brand copy stay editable without a developer
  • Filters cover bedrooms, baths, price, neighborhood, pets, and features
  • Map and list views stay in sync as filters change
  • Filter state survives the back button from a unit page
  • Empty results and stale data both have a defined screen
  • One page per available unit, created and retired by Yardi
  • Photos, floor plan, price, terms, and square footage from RentCafe
  • Apply and inquiry buttons hit the correct RentCafe URL
  • Street and neighborhood context sits above building details
  • Our Story, FAQ, contact, and the resident portal handoff
  • FAQ marked up so answers can surface in AI results
  • Fair housing, accessibility, and privacy pages in place
  • Keyboard navigation, contrast, and alt text checked against WCAG AA
  • Contact form routed to the right leasing inbox with spam protection
  • Insider's Club email capture feeding a Customer.io welcome sequence
  • Submissions land in Customer.io, not an unmonitored inbox
  • Validation and confirmation messages on both forms, server side too
  • Headless CMS your marketing team runs for about $30 monthly
  • Content models for neighborhoods, FAQ entries, and page metadata
  • Editors change copy and metadata without touching code
  • Preview before publish, so nothing ships by accident
Part 01 subtotal10h27h
SRM Urban · Website and Yardi08
06 · The scope · Part 02 of 02

What makes it work,
and project overhead.

#ItemTypeDesignBuild
  • OAuth token refreshed inside Yardi's eight hour window, with a lock
  • Per-property rate governor keeps calls under Yardi's daily ceilings
  • Fast lane for availability and pricing, slow lane for setup data
  • Last known good data serves if Yardi returns an error
  • One internal shape for units, so the front end never parses Yardi
  • Refresh cadence set per property, not one global setting
  • Swapping or adding a data source later touches one layer
  • Transaction counts logged against your in-house Yardi license, not ours
  • Tag Manager container with events for inquiries, applies, and filters
  • GA4 reporting configured against that event model, not defaults
  • Google and Meta retargeting pixels installed and verified firing
  • Customer.io connected for lead capture and follow-up sequences
  • Staging and production on your own cloud, with preview builds
  • Rollback path tested before the launch, not after
  • Uptime and error alerts on the integration, not just the site
  • Launch day walkthrough with whoever will publish content
Part 02 subtotal0h32h
+Project Management15% of total0h10h
+Design Review10% of design2h0h
+QA and Testing20% of build0h12h
Project total · 93 hours · $13,000 base12h81h

Assumes RentCafe stays the data source through launch, and that unit photos already live in Yardi rather than only in WordPress.

SRM Urban · Website and Yardi09
07 · Add-ons

Add what you need.
The price is fixed either way.

Switch any add-on on to see the new total. Each one is fixed price, and you can add it now or after launch.

Neighborhood Pages

$7506 hoursSame timeline
  • One template covers all eighteen neighborhoods, not eighteen pages
  • Available units in the area list themselves from live data
  • Local copy and imagery editable in the content system
  • Per-neighborhood metadata for local and AI search results

SEO and AEO Foundation

$1,0008 hoursSame timeline
  • Metadata and canonical URLs per template, not per hand-built page
  • Structured data for listings and neighborhoods, readable by AI search
  • Redirect map so existing unit URLs keep the traffic they have
  • Sitemap and robots file generated from the live inventory

MRI URL Migration Script

$1,1508 hoursSame timeline
  • Takes the spreadsheet your team would otherwise work through by hand
  • Rewrites every MRI Prospect Connect link to its RentCafe equivalent
  • Runs before launch, so current listings work in the meantime
  • Re-runnable, so a second pass costs you nothing

On-Call Engineer, 3 Months

$2,25015 hoursAfter launch
  • 5 hours a month of a named engineer for 3 months after launch
  • Yardi refresh failures, 429s, and stale listings handled same day
  • Content system questions answered without opening a new project
  • Unused hours do not roll over, and nothing auto-renews
Your total $13,000 · 93 hours · 12 weeks
SRM Urban · Website and Yardi10
Next step

Ready when you are, Matt.

You get SRMurban.com rebuilt on Next.js, Yardi feeding every listing, and the tracking stack live. That's 12 weeks at $13,000 for the base, billed half at signature and half at launch.

We built the site you're running today and we've kept it up since launch. Tell me which add-ons you want, if any, and we'll lock the kickoff date.

Contact

Brian Hammond
VP of Sales, FYC Labs

Reach me

bhammond@fyclabs.com
fyclabs.com

Proposal valid 30 days · 10.7.2026fyclabs.com