Smart Building Software Development

Smart building software for facilities decisions across disconnected systems.

We connect selected HVAC, lighting, metering, access, occupancy, and service data to a shared facilities workflow. The safer first release is usually read-only: prove point quality, alerts, and response ownership before considering remote control.

See our work

Bring the problem, the current workflow, or the existing code. We reply with a practical next step within one business day.

The brief

Start with what is not working.

Good software decisions begin with the constraint, not a list of features or a preferred technology.

01

Do facilities teams switch between vendor portals without one trusted building state?

02

Are energy, comfort, access, and maintenance events visible but not connected to an owned response?

Plain answer

Smart building software connects selected HVAC, lighting, metering, access, occupancy, and service data to facilities workflows. RaftLabs builds integration and operating software around installed systems, with read-only monitoring as the safer starting point. A focused release for two systems in one building starts at $35,000 and usually takes 12 to 16 weeks.

Every system had data. Nobody had the building state.

Every system reported. HVAC, meters, access, and service requests still lived in separate tools. A useful shared view connects an accepted event to the facilities or tenant-service team responsible for the response, with enough context to respond safely.

Focused delivery baseline

starting first release
$35K
Priced after installed-system access is verified
typical focused timeline
12-16 weeks
One building and two system paths
preferred initial authority
Read-only
Control requires a separate safety decision

RaftLabs does not currently publish a named smart-building outcome case. These are scope and delivery parameters, not promised energy or service results. The first release should use an agreed site baseline and report any measured change against the building, operating period, and recorded intervention.

Build custom smart-building software when disconnected systems block a specific facilities workflow.

Start with one building, representative points, a named response owner, and the lowest useful authority.

A fit
01

The installed vendors, gateways, points, licenses, and data rights can be inspected.

02

A facilities, energy, maintenance, or tenant-service response has an owner.

03

Existing portals cannot provide the shared context or workflow the team needs.

Not a fit
01

A current BMS or property platform already covers the required view and response.

02

The request assumes control writes without approved interlocks and manual override.

03

No baseline or responsible team exists for the proposed alert or optimisation.

Choose the first building operating mode

ModeBest fitConstraint to settle
Read-only monitoringTeams need shared state, trends, and fault evidencePoint quality, timestamps, naming, and access
Workflow integrationAccepted events should create maintenance or tenant workOwnership, deduplication, priority, and outage handling
Remote controlApproved schedules or setpoints should change automaticallyInterlocks, safe range, override, rollback, and audit

Scope

What belongs in a focused smart-building release

  • 01

    Installed-system integration

    Connect selected BMS, HVAC, lighting, meter, access, occupancy, or service sources through approved interfaces.
  • 02

    Normalized building data

    Map points to building, floor, zone, equipment, units, schedules, and quality so sources can be compared.
  • 03

    Shared operating view

    Show current state, trends, exceptions, and source health for the facilities team responsible for the response.
  • 04

    Fault or service workflow

    Route an accepted event to maintenance or tenant service with context, ownership, status, and audit.
  • 05

    Measured intervention

    Record baselines, changes, operating periods, and results without presenting a generic saving as a site outcome.

How it works

From building inventory to operating pilot

  1. Phase 1
    01

    Choose the operating decision

    Select one building, two systems, the facilities response, baseline, authorised users, and required authority.

  2. Phase 2
    02

    Verify interfaces and control boundaries

    Inspect vendors, protocols, points, gateways, network zones, data rights, and read or write permissions.

  3. Phase 3
    03

    Build the shared view and workflow

    Normalize selected points, add trends and alerts, and connect the event to maintenance or tenant service.

  4. Phase 4
    04

    Pilot and measure

    Run representative schedules and faults, compare with the baseline, tune alerts, and document support ownership.

Risk

What the building integration specification must settle

Vendor access
Confirm gateways, credentials, licenses, protocols, supported points, and rights before promising the path.
Point quality
Sample naming, units, timestamps, gaps, overrides, and schedules before defining analytics or alerts.
Control authority
Separate observation, recommendation, service work, and writes, with explicit approval for each level.
Response ownership
Name who receives events, works them, handles false positives, and supports the integration.

Scope and price

A focused smart-building release starts at $35,000.

Begin with one building, two installed systems, a shared view, and one facilities workflow.

The first phase proves point quality and response ownership before more systems or sites are added.

Starting investment

Starts at $35,000

A focused first release usually takes 12 to 16 weeks. More buildings, tenant features, analytics, or control authority extend the plan.

Access verified first

The proposal names each installed-system path and calls out any interface that needs a technical proof.

No borrowed savings claim

Energy or service outcomes are reported only against the agreed building baseline and recorded intervention.

Related IoT services

Common questions

The scope may include HVAC and BMS controllers, lighting, meters, access control, occupancy sensors, tenant systems, and CMMS or property software. We verify the installed vendor, protocol, licenses, gateway, points, and data rights before promising an integration.

It can expose schedules, loads, and faults that merit investigation, but software alone does not guarantee savings. We agree a site baseline, record the intervention, and compare like operating periods so the facilities team can attribute any measured change.

These protocols can be in scope, but protocol support does not guarantee access to every installation. The actual path depends on the installed controller, vendor license, gateway, network policy, point availability, and whether the owner permits read-only or write access.

Usually not when point naming, schedules, interlocks, vendor access, or operating responsibility are unclear. Read-only monitoring can prove data and response workflows. Add control only after the owner approves commands, safe ranges, fallback, audit, manual override, and rollback.

A focused release starts at $35,000 and usually takes 12 to 16 weeks. It covers one building, two installed systems, a shared operating view, one alert or service workflow, and one downstream integration. More buildings, tenant features, analytics, or control authority increase scope.

Work with us

Bring one building decision that crosses two systems.

Share the installed vendors, protocols, available points, facilities users, baseline, downstream workflow, and allowed authority. We will identify the smallest safe release.

  • Scope and cost agreed before work starts. No surprises. No obligation.
  • Working prototype within 3 weeks of kickoff.
  • Pay by milestone. You see progress before each invoice.
  • 60-day post-launch warranty. Bug fixes, UI tweaks, and deployment support. No retainer.
  • All conversations are NDA-protected.