Page flooring & concrete solutions

Five systems, three logins, and a dozen workarounds, replaced with one platform they own.

Page Flooring was paying prices for software that didn't do what their business does. We consolidated the whole stack into one piece of software built around their workflow – then gave the company a face that matched what it had become.

page flooring hero image
Client

Page Flooring & Concrete Solutions

Sector

Commercial flooring & concrete

Base

813 Brock Rd, Pickering, ON

Engagement

Platform • Brand system • Website

Outcome

One system of record, built for how flooring actually works.

They came to us running the business across five systems that didn't talk to each other. We replaced the whole stack with one piece of software they own – with the financial layer integrated rather than reconciled.

outcome

One system of record

Projects, financials, and documents in one place instead of scattered across tools that don't talk

Their process, not a vendor’s

Features built for how flooring works: schedules of values, sample transmittals, change orders. No more workarounds bolted onto generic software.

An asset on the balance sheet

Software the business owns and controls, and the data to go with it. That’s enterprise value, not an expense line.
Problem

They were paying a premium for software that couldn't say yes.

Page Flooring ran on enterprise software, the real kind with the real price tag. When they asked for the small, specific things their business needed, the answer was no. Nothing was impossible; it just wasn't on the roadmap

So they did what every capable operator does: they built around it. A board tool here because the main system couldn't track projects the way they work. A spreadsheet there. A manual process to bridge the gap between the system that holds the money and the system that holds the job. Each one was a smart fix. Together they became the problem.

Data lived in four places, which means it lived in none of them. Reconciling anything meant human. They were paying for multiple platforms, paying people to keep those platforms in sync, and still looking at building new things to fill the gaps left over. The workaround stack cost more than the software it was patching.

In this industry the gaps were in the most expensive place. The name of the game in the trades is paying and getting paid: purchase orders, bills of lading, schedule of values, progress billing, lead times on material ordered months before it's installed. It is transactional work that behaves like a service business, and generic project software doesn't understand any of it.

Very knowledgeable team! I must say from the start of our dealings right up until the end - I was thoroughly impressed with their communication, efficiency and ability to listen to our needs and translate that into a finished product! Highly recommend using OpenCore!

Dylan PagePage Flooring
The stack, before and after
before
Process

You can't design a better process until you understand the one they have.

The work started in their building.

01

On site, with their people

Our team sat with theirs across estimating, project management, accounting and the field, and with leadership. Different people, different truths.

EstimatingProject managementAccountingFieldLeadership
02

Map what happens today.

Including every manual workaround built over the years to patch a gap. Those workarounds are documentation: each one marks where the old system failed.

03

Understand the history.

How they’ve always done it, and how they do it today. Those are rarely the same thing, and the difference tells you what’s essential and what’s leftover.

04

Build in their channel.

Shared chat, continuous feedback, functionality in front of them while it’s still cheap to change.

Process map
5 DEPARTMENTS · 1 JOB, START TO FINISH
process img
Drawn from the on-site sessions. The orange bars are the inventory of workarounds — and the build order came straight off them.
Solution

One platform, built around the way the work actually moves.

We took everything they were stitching together and built a single system they can scale, customize and control, with the financial layer integrated rather than reconciled.

Project management kanban board
01

Schedule of Values

Progress billing that matches how the industry actually contracts, with two-stage locking so figures can’t move once they’re committed, and clean export for anyone who still needs it in a spreadsheet.

02

Financial integration

The accounting system stays the source of truth for the books, and the platform talks to it directly. Invoices, POs and progress billing stop being a re-typing exercise.

03

Sample transmittals, change orders, IFC drawings

The documents this trade runs on, built into the platform rather than attached to a generic task tool.

04

Role-based access and single sign-on

The field sees what the field needs. Finance sees what finance needs. One identity, tied to the systems they already use.

The data model in plain language. Connected records, not four exports

solution img 6
Under the hood, a relational data model that reflects the business, with jobs, values, documents and money as connected records rather than four disconnected exports. Scheduled jobs handle the syncing people used to do by hand. Protected, permissioned interfaces mean every part of the platform reads from one source of truth.
Note on disclosure

We stay deliberately non-specific about our stack in public. Naming every component of a client’s architecture is a security disclosure, not a portfolio piece.

results

One platform, built around the way the work actually moves.

Multiple paid platforms consolidated into one owned system.
Manual reconciliation between project tracking and accounting eliminated.
Features the previous vendor declined to build are now live.
The business owns its software and its data, which changes what the company is worth to an acquirer.

Have question? We've got answers!

It depends on scope, but most website projects run four to eight weeks, and custom software projects typically run two to four months for a first version. We work in stages, so you're seeing real progress early rather than waiting for a big reveal at the end. Before we start, we'll give you a clear timeline with milestones — and because most of our clients work with us on a retainer, the launch date is usually a starting point rather than a finish line.

Didn't find the answer?

Book a call and let's have a chat.

Tell us what you're building.

We'll help you map the right scope, team, timeline, and next steps

Start your new project