Qaynaq STUDIO ’26 / BAKU
Work FW038

Ecohome · Real estate & construction · 2026

Customer-facing site and back-of-house systems for Ecohome

A premium residential complex needed one team to own both the public website and the operational stack behind it. We built the site, the ERP, the firewall and data servers, the biometric access layer, the network, and the social-media presence — under one programme.

Duration
Multi-phase
Team
Elvin Şərifov + Bəhram İbadov
Services
Website · ERP · Firewall server · Data server · Social media · Biometric access · Networking
Status
Live

Starting point

Ecohome was launching a premium residential complex where the marketing surface and the operational reality had to feel like the same brand. A polished public site is no use if the access gate is unreliable and the leasing team is running on spreadsheets — the customer experience has to hold from the first click through to the day they move in.

The studio was hired to own both sides. Bəhram İbadov led the on-site infrastructure — firewall, data server, network, biometric access — while Elvin Şərifov led the public site, the ERP rollout, and the social-media build. One brief, one team, one accountable result.

Decisions

  1. Treat the residence as a single system — the website, the ERP, the door, and the network are not separate vendors; they share identity, policy, and a single point of ownership.
  2. Firewall server in front, data server behind — resident data, tenancy records, and operational logs live on a hardened tier with documented access policy, not on a sales laptop.
  3. Biometric access tied to the resident record — when a tenancy starts or ends in the ERP, access at the gate updates with it; no parallel list to fall out of sync.
  4. Public site as a sales surface, not a brochure — the website is structured around the actual leasing funnel, with content and analytics tuned around enquiries that convert.
  5. Social media as a continuous channel — the SMM stream is operated alongside the site rather than spun up only for launches, so the brand surface stays alive between phases.

Execution

Infrastructure went first — the firewall server, data server, and on-site network — so that everything downstream could trust the layer underneath it. ERP came next, with the leasing, finance, and operations workflows defined alongside the team that would actually run them. The website and biometric access were brought online in parallel and tied back to the ERP record, and the social-media programme was handed over with a content cadence the in-house team could keep running.

"A premium address has to feel premium at the gate, in the leasing office, and on the site. One stack, one team — that is the only way that consistency survives the second year."
— Elvin Şərifov + Bəhram İbadov

Result

  • One operational system — site, ERP, gate, and network share identity and policy.
  • Hardened on-site stack — firewall and data server documented, segmented, and reviewed.
  • Biometric access wired to the resident record — tenancy changes in the ERP flow through to the door.
  • Website operated as a sales surface — structured around the funnel rather than the org chart.
  • SMM running continuously — the brand surface stays alive between phases.

For a project like this,
let's talk.

Email Elvin Şərifov + Bəhram İbadov