KMV Construction
Designing Juntos: bringing the construction supply chain onto one bid platform
Juntos is a mobile bidding platform that KMV Constructions built to run its own procurement across vendors, subcontractors and KMV’s subdivisions, and planned to white-label as a subscription product for other companies.
Bids used to be settled by phone, with no record of what was agreed. In three weeks, I designed the full experience as a review and trust layer around the bid. Vendors submit multi-product bids themselves. Every revision is logged with who made it and why, and terms and conditions keep both sides accountable. Purchase orders and shipment notices live in one searchable history. I designed it so a person can always see what changed and trace it back.
ROLE
UI / UX Design
SCOPE
Visual Design
Brand Strategy
Design System
TIMELINE
Aug 2024 - Oct 2024
OUTCOME
How might we give construction teams a clear record of every bid decision, so they spend their time building, not chasing paperwork?
Construction material bidding at KMV was largely manual. As procurement scaled, these gaps stopped being inefficiencies and became operational blockers.
No record of what was agreed: Pricing was negotiated by phone, with no audit trail.
Information everywhere: Vendor quotes, revisions and availability were scattered.
No source of truth after the bid: POs and ASNs had no central home.
Costly coordination: Manual follow-up caused delays, errors and budget risk.
Design a vendor-facing bid management experience that:
Lets vendors take part in bidding on their own
Documents negotiations, revisions and approvals end to end
Centralizes ASNs, POs and contractual records
Is production-ready and feasible to build in a compressed timeline
THE OBJECTIVE
01
Juntos digitizes the three procurement workflows that mattered most.
Bidding: Vendors submit, revise and manage multi-product bids digitally.
Negotiation: Revisions are structured, with full traceability and accountability.
Documentation: Bids, ASNs, POs and contracts are kept as persistent records.
02
Core Workflow : Advance Shipment Notices (ASNs)
An ASN captures shipment details: materials, quantities, delivery timelines and logistics. It was handled manually, especially for new vendors, which caused delays and inconsistencies. I designed the system to support today's manual input while laying the groundwork for ASN automation later.
03
Who it's for
Construction managers review incoming bids, negotiate through revisions and need to know what was agreed.
SPOCs and admins are the single point of contact between KMV and its vendors. They keep the bid, PO and ASN records in order and answer for them.
Vendors and sellers submit and revise multi-product bids and follow them through to purchase orders.
Material manufacturers supply the materials and enter shipment details through ASNs.
DESIGN SYSTEM & UI STRATERGY
Design System
Once the app's structure was set, I built a design system so screens could be made quickly and look and behave the same way.
What it includes:
• 50+ reusable components
• Defined variants, states and interaction rules for each
• Set values for type, spacing and color
• A sticker sheet for assembling screens fast
With one shared set of parts, design and engineering could work in parallel, and the result stayed consistent and predictable.
BULDING THE PRODUCT
Solving the biggest hurdle: multi-product bids
Vendors rarely quote one item. They quote a set of materials, and pricing them together was the part they struggled with most. A bid flow that handled one product at a time would have kept the phone call alive.
Revisions and negotiation
Prices move during a negotiation, and the final number used to live in someone's memory. I designed revisions as part of the bid itself. A revision log records every change made by the vendor or the client (the construction manager), with older revisions loaded on demand so the current one stays in focus.
Terms and conditions carry the nuance. Each term, such as packaging and forwarding, credit costs, defect during transit, loading, unloading and transit insurance, is set on its own. Where a term is declined, the person picks a reason. That lets nuanced agreements be held accountable.
Defining where records live
After a bid is won, the paperwork still has to be findable. ASNs and POs, along with their PDF copies, are kept in a searchable, retrievable history and can be downloaded easily.
Each ASN card shows the shipment number, what is being supplied, the linked PO, the site, and the delivery date and time. Item details list quantities, and two actions sit at the bottom: view the proforma invoice and view the linked PO. Shipments are split into Upcoming and Delivered, and a new ASN can be created from the top of the list.
Putting it all together
The app is organized around the work: Home, Bids, Orders, ASN and Profile. The same screens work as a standalone mobile app and inside KMV's vendor management ecosystem.
What shipped was mapped to how the business works
All design outputs were mapped to KMV's business logic and operational flows, so the system was functionally complete and ready to implement. That meant:
End-to-end UI flows aligned to the bidding, negotiation and documentation business rules
Component behavior definitions covering states, edge cases and error handling, tied to real procurement scenarios
Interaction patterns stress-tested against high-volume and multi-product use cases
Engineering-aligned specifications, refined through real-time feasibility reviews and feedback loops