Home

Above-the-line (ATL) Markups — Ediphi

Customers often need to include costs tied to subsets of line items — like insurance, compliance fees, or jobsite utilities — not just the overall project total. Ediphi’s original markup feature worked only “below the line,” applying formulas at the aggregate level. To meet customer demand, we introduced Above-the-line Markups, which allowed markups at the line-item level, applied before below-the-line calculations. This gave estimators finer control and more realistic forecasts in the preconstruction phase.

Back to Projects

Adding a Markup to an Estimate

Tech Stack: Express Node Javascript Typescript Jest Playwright React Redux
My Role
  • Served as co-Epic Anchor (mentoring a teammate stepping into project leadership).
  • Partnered with Product & UX to design a markup system flexible enough for customer-specific workflows while still standardized.
  • Prototyped dozens of markup models in Google Sheets to validate formulas and behaviors.
  • Implemented parts of the solution including Alternates handling and visibility logic across the app.
  • Managed dependencies with other initiatives (ColumnBuilder, exports to PDF/Excel, external integrations).
Impact
  • Directly helped close deals with at least 3 new customers.
  • Showcased at an estimating conference, where Ediphi’s booth became the most popular vendor stand, fueling pipeline growth.
  • Influenced the creation of a dedicated Data Integrity team, tasked with monitoring calculations through a new Calculation Engine.
Technical Highlights
  • Designed a system where markup allocations are defined but not redundantly stored in the database, avoiding exponential growth in data.
  • Balanced customer-specific flexibility with system-wide maintainability.
  • Integrated ATL Markups into Estimates while solving for Alternates logic, a feature customers insisted could not be deferred.
A Story
Just as we were preparing for release — scope reduced, bugs triaged, comms drafted — the CTO mandated that we address Alternates before launch. This pivot added three months of design and delivery, straining morale but ultimately deepening our understanding of Estimates and enabling stronger sequencing for future projects. For me, seeing my teammate evolve from “coder” into a customer-focused Epic Anchor — asking questions about why customers needed features — was one of the most rewarding outcomes.
Docs