LIVE CLIENT WEBSITE

Atlas Midlands Holdings

A public brochure and enquiry website for Atlas Midlands Holdings, a Midlands property management company. The project gives landlords, tenants and people with maintenance questions clearer starting points. It explains the offer and directs enquiries to the business. The current delivered scope is a website, with private portals and CRM functions outside this case study.

Original AAG editorial concept illustration. This is not a photograph of the client premises or an actual product.
Editorial illustration. Not a photograph of the client premises or a released product.

THE PROBLEM & THE PURPOSE

One business, several reasons to visit.

Property management brings together people with different immediate concerns. A landlord may be considering an agency. A tenant may need information about an existing relationship. Someone dealing with a maintenance issue wants the appropriate contact route quickly. When those needs are mixed into a single undifferentiated page, visitors have to interpret the organisation before they can act.

The website separates those starting points. It presents the management offer, landlord and tenant support information, and maintenance information within one public structure. The aim of that structure is straightforward: let visitors recognise the route relevant to them without reading every other audience’s material first.

The page organisation is the delivered design response. Private property records, individual tenancy documents and account-based case tracking would require a separately scoped operational system.

PROJECT SCOPE

What the project contains.

A practical view of the scope at the stated stage.

01

Property management overview

The business can explain the management offer and provide a route for someone considering its services to make an enquiry.

02

Landlord and tenant routes

Public information is organised around different audiences. A prospective client and an existing occupant should not have to start with the same question.

03

Maintenance information

A visitor can find the relevant public information and contact route. This case study does not imply a private maintenance ticketing or emergency dispatch system.

EXPLAINED VISUALLY

The right starting point for each visitor.

This original audience map shows how the public information is grouped. It is not an internal system map or a screenshot of property records. No personal tenancy information appears in the diagram.

The right starting point for each visitor.. This original audience map shows how the public information is grouped. It is not an internal system map or a screenshot of property records. No personal tenancy information appears in the diagram.Open the blueprint

DESIGN DECISIONS

Organise around the visitor’s question.

An audience route is useful when it leads to meaningfully different information. Simply adding more menu headings can make navigation harder. The public structure needs to answer the question behind each route, with enough context for visitors to know whether they are in the right place.

Maintenance content also needs clear boundaries. A general web enquiry and an urgent repair are not automatically the same service. Contact instructions should reflect the operator’s actual process rather than implying monitoring or response arrangements that have not been established.

A later portal would change the design problem. It would need individual access, reliable record ownership, a defined upload process and permission checks. The customer portals service describes how that separate scope can be considered.

EVIDENCE & LIMITS

What this project demonstrates.

The Atlas Midlands public website provides the reference for the delivered brochure pages. This project record explains the public structure and its purpose. It does not reveal landlord lists, tenant details, maintenance records, commercial terms or private correspondence.

No reduction in administrative time, response-time improvement or increase in leads is claimed. Such results would need an agreed measurement method and appropriate permission before publication.

OUR TAKE

The useful lesson.

A useful property website does more than introduce a company. It helps a visitor find the information that matches their relationship with it. That public clarity can be valuable before any private software is needed. Read about our property websites and customer portals for the distinction between the two layers.

DETAILS

Project questions.

Is Atlas a CRM or customer portal?

The delivered scope described here is a public brochure and enquiry website. Account-based records and CRM functions are not claimed.

Why separate landlords and tenants?

They commonly arrive with different questions. Audience routes make the relevant information easier to recognise without exposing private records.

Can you publish the private operating screens?

No private operating screens or personal property records are needed to explain this project. The public case study uses an original schematic instead.

LET’S TALK

Discuss a similar project

Tell us about the people using the result, the task that is difficult today and what a useful first release should do.

Start a conversation