Skip to content
Zaman Javed.
All work

Construction Sales CRM

A CRM built exclusively for the construction industry — voice-first data entry, bid-to-invoice pipeline tracking, and deep Outlook + ERP integrations that replace the industry's spreadsheet habit.

Client work under NDA — product name and screenshots withheld.

Role
Senior Full-Stack Engineer
Where
MavricTeam
Timeline
2024 — Present
Stack
LaravelPHPVueMySQLVoice AIREST APIs

0+

construction ERPs integrated — Sage, Viewpoint, Foundation

0%

pipeline visibility, first bid to final invoice

0

spreadsheets left in the sales workflow

Overview

A customer relationship management platform built exclusively for the construction industry — subcontractors, general contractors, and their sales teams. It tracks every opportunity from first bid through final invoice, with reporting on close rates, pipeline status, and team performance in real time.

I've been building it since 2024 as a senior full-stack engineer on the team at Mavric — an active, services-driven product where we ship new features and integrations on a rolling basis. It's a client product, so the specifics here stay generic.

The industry context matters: construction runs on relationships and phone calls, not desk time. A CRM that demands typing after every site visit simply doesn't get used.

Problem

  • Sales teams tracked bids in spreadsheets — no shared visibility, no follow-up discipline, deals quietly dying between versions of the same file.
  • Generic CRMs failed here before: data entry friction meant estimators and field reps never logged anything, so the pipeline was fiction within a month.
  • Bid data lived apart from the money: the ERP (Sage, Viewpoint, Foundation) knew about invoices, the spreadsheet knew about bids, and nobody saw the whole picture.

Approach

Adoption was treated as the product requirement, not a hope. The PRD framed one blunt success metric: does a field rep actually log activity without being chased?

That framing drove the headline feature — voice-first data entry. A rep describes what happened after a site visit in plain speech, and the AI logs the activity, links contacts, and updates the deal — no typing, no forms. Outlook integration does the same for email: messages auto-log against the right contact and opportunity.

The build followed a documented process: workflow, stage, and permission models designed first (every construction company runs its pipeline differently, so customization is schema, not code changes), then integration contracts for the ERP connections, then feature delivery in scoped, reviewed increments.

Key decisions

  • Voice as the primary input, not a gimmick — the AI data-entry path got first-class treatment because it is the difference between a CRM that's used and one that's abandoned.
  • Customization as configuration — fields, stages, and permissions are data, letting each contractor mirror their real process without forked code.
  • Meet the money systems where they live — integrations with construction ERPs (Foundation, Viewpoint, Sage) rather than asking companies to migrate; the CRM completes the picture instead of fighting it.

Outcome

Sales teams get what the spreadsheet never gave them: one live pipeline from bid to invoice, follow-ups that actually happen, and dashboards that report reality because logging activity costs nothing. The platform is live in production and serves construction teams across the U.S.