Skip to content

Concept project 01 Architecture

A property website the sales team runs itself

A bilingual site for a residential developer, built so that apartments, prices and availability are kept current by the people who sell them.

Company
Concept project · fictional developer
Industry
Residential property
Layer
Architecture: Digital architecture, Custom software
Services
  • Web design
  • UX/UI design
  • Custom software

Invented company and sample data, no client results

Concept project
Language of the sample page

Sample data: Project page with filters and the live status of every apartment. Switch the page between English and Bulgarian in its header.

Sample data: The unit editor the sales team uses. Shared facts are entered once, the words in both languages side by side.

Sample data: Floor plan of level 4, with the apartment from the editor selected.

See each screen up close

01Overview

The concept, in short

A residential developer is selling the first building of a project in Sofia: six floors of apartments, offered to buyers in English and Bulgarian. The sales office knows the status of every apartment within the hour. The website learns it days later, if anyone remembers to ask.

The concept treats the website as part of the sales process rather than a brochure: the people who sell the apartments keep it current themselves.

Objective

A site the sales team keeps current in both languages, from one set of data, with no developer in between.

02Challenge

What is in the way

Four problems, and each one makes the next one worse.

  1. 2.1Operational problem

    Every change waits in a queue

    A new price, a reservation or a sale goes to an outside developer as a request. The site is often days behind the sales office.

  2. 2.2Growth limitation

    Buyers cannot find their apartment

    There is no way to filter by floor, size or orientation, so even simple questions come in by phone and the site does little of the selling.

  3. 2.3Workflow bottleneck

    Two languages, two copies

    English and Bulgarian are separate copies of the site. Every edit has to be made twice, and the two versions drift apart.

  4. 2.4Constraint

    Sellers, not editors

    The people who know the status are salespeople. An update has to take them a minute, not a training course, and the pages still have to be fast on phones and readable to search engines.

03Solution

One record for every apartment

We start from the data, not the pages. When every apartment is one record that the sales team owns, the listings, the filters, the floor plans and both languages are built from it, and the site can no longer disagree with the sales office.

1Edited by

  • The sales team, in the unit editor
  • Shared facts once, the words in each language

2One record

Apartment A-403Sample data

Building
A
Floor
4
Rooms
3
Area
96.4 m²
Orientation
South-east
Price
€197,600
Status
Available
Title
ENThree-room apartment with a south-east terraceBGТристаен апартамент с тераса на югоизток

3Where it appears

  • Project page, in English
  • Project page, in Bulgarian
  • Floor-plan view
  • Filters and search results
  • Enquiry form, with the apartment's reference
  • Structured data for search engines
How the concept fits together: the sales team edits one record per apartment, and every page that shows the apartment reads from it.

What we would build

  1. 3.1

    A content model for buildings and units

    Every apartment is one structured record: building, floor, rooms, area, orientation, price and status. Listings, filters and floor plans are all generated from it.

    See screen C

  2. 3.2

    An editor made for the sales office

    One screen per apartment, holding only the fields the sales team actually changes. Status is a single control, and saving updates every page the apartment appears on.

    See screen B

  3. 3.3

    English and Bulgarian from one place

    Area, floor and price are entered once. Only the words are translated, side by side, and the apartment goes live in both languages together.

    See screen B

  4. 3.4

    Listings buyers can filter

    Filters for rooms, floor, area, orientation and status, and a floor-plan view in which every apartment shows its current status.

    See screen A

  5. 3.5

    Fast pages, built for search

    Pages rendered on the server, with readable addresses in each language, structured data for every apartment and images sized for phones.

    See screen A

04Screens

Three screens from the concept

Built in the browser for this page, with sample data throughout. Screen A switches between English and Bulgarian in its own header.

Invented company and sample data

Public site

The project page

Project page with filters and the live status of every apartment. Switch the page between English and Bulgarian in its header.

Language of the sample page
A.1Status, set by the sales team The apartment edited in screen B is listed as available and marked as updated today.
A.2An address in each language Each floor and apartment has a readable address in English and in Bulgarian, rendered on the server.

Sales office

The unit editor

The unit editor the sales team uses. Shared facts are entered once, the words in both languages side by side.

B.1One control for status Available, reserved or sold: one click, and every page that shows the apartment changes. The price per m² is calculated, not typed.
B.2Both languages side by side Only the words are translated. One save publishes the apartment in English and Bulgarian together.

Public site

The floor plan

Floor plan of level 4, with the apartment from the editor selected.

C.1The same apartment, on the plan The plan reads its colours from the same records, so a buyer sees what the sales office sees, terrace included.

05What changes

What changes for the people using it

A concept has no results to report, so these are the changes the design is built to make. On a client project, confirmed figures take these places.

  • 5.1Sales team

    No queue

    The sales team changes a status the moment a deal moves, without writing to anyone.

  • 5.2Buyers

    One status, two languages

    Buyers see the same availability as the sales office, in their own language.

  • 5.3Enquiries

    About one apartment

    Enquiries arrive about a specific apartment, with its floor and price already known.

  • 5.4The developer

    New building, no new pages

    A new building is added by entering its data, with no new pages to commission.

06How we would work

The five steps, applied here

Clarity throughout: clear goals, an agreed scope, one line of communication and a short report at every step.

  1. 01

    Discovery

    A morning in the sales office: how a reservation is recorded today, and who is asked to change the site.

  2. 02

    Strategy

    Agree the record first: which facts are shared, which words are translated, and which pages read from it.

  3. 03

    Design & Execution

    The editor and the public pages are designed together and reviewed with the sales team on working versions.

  4. 04

    Optimisation

    We watch which filters buyers use and which questions still come by phone, then adjust.

  5. 05

    Scale

    The next building is added as data. The team gets a short guide and runs the site itself.

Concept project. The developer, the building and every figure on the screens are invented for illustration.

→Examples

More examples

All examples

→Next step

Tell us what you are building

Write or call. Tell us where the business is going and what is in the way, and we will suggest where to start.

Email us

or call +359887185254

A few lines are enough

  • What the business does and who it sells to
  • What you would like to change, and why now
  • Any date that matters, such as a launch or a season

Cookies on this site

Choose whether to allow analytics and interactive maps. Necessary code helps provide the service you request.