HOLLOW POINT
Contact
Get In Touch
Dubai: +971 588130712UK: +44 7814173588hi@hollowpoint.io
TRACK A · WEB + OPS SYSTEM/ case-studies / property-operations-platform

SEO-first website and operating system for a property operator.

This anonymised property operator needed a serious web presence for supported living and temporary accommodation, plus a practical operating layer for the portfolio behind it. We shipped the live site, SEO service pages, city landing pages, lead capture and the runbook-style operations system around a real property business.

LiveNext.js site on Vercel
9City / area SEO pages shipped
28Units represented in portfolio context
OpsRunbooks, liaison pack, compliance workflows
§ 00  —  OPERATOR BRIEFcase summary
CLIENT
Anonymised UK property operator
property / supported accommodation
PORTFOLIO
5 properties / 28 units
West Midlands + Derbyshire
OPERATING TEAM
Small, deep operational surface area
—
WEBSITE
SEO-first service pages + city pages + lead capture
live
OPS SYSTEM
Liaison pack, forms, compliance docs, finance context
runbook-led
§ 01  —  CONTEXT

The business.

The client is a property business operating HMO and supported accommodation assets across the West Midlands and Derbyshire. The portfolio context is real: multiple properties, 28 units, provider relationships, local authority relevance, tenant liaison, compliance obligations and a commercial need to keep the pipeline warm.

The website had to do more than look credible. It had to explain the offer to referral partners, providers and local stakeholders, target the right service searches, and create a professional digital surface for a business that depends on trust.

Behind the public site, the same business needed practical operating structure: documents, liaison packs, forms, compliance logs, rent/remittance tracking context and repeatable runbooks. This is the same pattern as our ecommerce work, applied to a property operator.

——
§ 02  —  BRIEF

Three things, agreed in writing at the end of scoping.

One — a public-facing website that makes the business legible. Supported living, temporary accommodation, mental health supported housing, young adults, city coverage, contact paths and trust signals. The site had to help the right people understand the offer quickly and enquire with context.

Two — an SEO foundation for local and service intent. Pillar pages for the core services, city/area pages for geographic relevance, metadata and schema in place, sitemap submitted, and a structure that can support a blog/content layer later.

Three — operations tooling for the weekly work. Liaison packs, property visit forms, incident reports, end-of-day forms, fire and safety logs, tenant communications, compliance tracking, remittance context. Previously scattered across Word, Google Docs, email, Drive and spreadsheets.

——
§ 03  —  WHAT WE BUILT

One coherent platform, three surfaces.

01

SEO-first public website

Next.js 16 on Vercel. The public site explains the service model, gives referral partners and stakeholders a credible place to land, and targets the searches the business needs to be visible for: supported living, temporary accommodation, mental health supported housing, young adults and local city/area combinations.

  • Server-rendered, edge-cached
  • SEO pillar pages for core services
  • 9 city / area landing pages
  • Lead capture routed to the business inbox
  • Sitemap and metadata shipped from launch
02

Runbook-style operations layer

The operational work was translated into runbooks and structured documents: property visits, incidents, end-of-day reporting, tenant liaison, fire and safety logs, and compliance records. One source of truth instead of a loose collection of documents that only make sense to the person who created them.

  • Tenant liaison onboarding pack
  • Google Forms specs for field reporting
  • Drive structure and Apps Script routing
  • Compliance and notice-board document pack
03

Finance and portfolio context

Built working context around the portfolio so the business can make decisions from the same facts: properties, units, voids, rent expectations, provider fee structure, remittance files and monthly payout state.

  • 5-property / 28-unit portfolio snapshot
  • Rent tracker and payout context
  • Fee structure notes and modelling assumptions
  • Next actions captured as operating priorities

This is the same runbook pattern we can build for any owner-led business: capture the operating context, define the repeated workflows, and give the team a system they can use without needing the founder to remember every detail.

——
§ 04  —  OUTCOMES

What the team feels on a Tuesday.

A credible web presence is live. The operator now has a proper website for the business, not a placeholder. The site explains the offer, supports local/service SEO, and gives partners and stakeholders a serious surface to evaluate.

Lead capture has somewhere to land. Inbound enquiries no longer rely on informal routes only. The website gives the business a controlled contact path and a foundation for future content, GBP and local SEO expansion.

Operating context is captured. Property data, portfolio status, fee structures, remittance context, liaison processes and compliance documents now live in project structure and runbooks. Less of the business depends on memory.

The build compounds. Stages 1-3 are live. The next layer is blog/content expansion and SEO polish, which can be added to an existing structure rather than rebuilding the site later.

ops.delta
 — BEFORE —
xWebsite:          no serious web presence
xSEO:              no service/city structure
xLead intake:      informal routes
xOps context:      docs + memory
 
 — AFTER —
+Website:          Next.js site live
+SEO:              pillars + 9 city pages
+Lead intake:      clear contact path
+Ops context:      runbooks + pack
——
§ 05  —  WHY IT MATTERS

The engineering pattern isn’t about ecommerce.

Most of our published work involves Shopify and ecommerce. This project proves the same systems approach works for a local service and property operator: web presence, SEO structure, lead capture, operating context and runbooks.

Different domain, same model. If you run an owner-led business where the website, the sales process and the operations process are all tangled together, there is usually more value in building the system around the business than in buying another isolated tool.

——
hollowpoint.io / contact

operator@hollowpoint:~$cat next-step.txt

Operational work eating your team?

If you've got recurring document, compliance or coordination work that doesn't need a person but currently has one — let's talk about whether a build fits.

AI engineering brief Talk to us
related —/case-studies/ai-engineering