A Construction Giant's Invisible Bottleneck
Adhi Karya is one of Southeast Asia's largest construction firms—the kind of company that shapes skylines and infrastructure across Indonesia. But size comes with complexity: hundreds of material vendors, multiple regions, projects that depend on reliable supply chains.
For decades, their procurement operated the way it always had: phone calls, emails, spreadsheets, manual approvals buried in layers of bureaucracy. Vendors were kept in the dark about pricing. Project teams waited weeks for approvals. Finance couldn't see cost trends. Nobody won.
Adhi Karya knew they could do better. They just needed to make procurement visible, fast, and fair.
The Hidden Tax of Invisible Workflows
Procurement isn't glamorous, but it's the circulatory system of construction. Miss a beat, and projects stall.
For Adhi Karya, the pain wasn't dramatic—it was systematic. When a project team needed materials, they'd submit a request. Someone in supply chain would email vendors. Vendors would respond with quotes—if they remembered.
Meanwhile, finance had no visibility into what was actually being bought or why prices varied wildly project to project. Approval workflows lived in people's inboxes, not in systems. A vendor couldn't see if their bid was competitive because they had no context. They just hoped.
1. The Costs Nobody Counted
Procurement cycles stretched across weeks and killed project momentum. Project managers couldn't plan confidently because they didn't know when materials would arrive or at what cost.
Vendors felt invisible—they competed blind, with no way to improve their offerings or pricing. Finance couldn't leverage volume discounts because no one had a complete picture of spend.
And compliance? It was a manual nightmare. Approval trails existed on paper and in memory, not in an auditable system.
2. The Deeper Problem: Procurement as Afterthought
The deepest issue was organizational. Procurement wasn't a strategic asset. It was something that happened to projects, not something that enabled them.
Nobody understood the workflow because it wasn't documented. It lived in people's heads and email inboxes.
Project delivery depended on procurement speed, but no one treated procurement as a competitive advantage.
3. The Real Question
How do you turn procurement from a cost center that slows you down into a system that accelerates you while making everyone—vendors included—more competitive?
Building a Marketplace Means Understanding How People Actually Work
Adhi Karya's vision was elegant: create a B2B marketplace exclusively for their vendors and project teams. Cut the middleman out of the equation. Let vendors list offerings. Let project teams see options, compare prices, and request approvals—all in one place. Let finance track spending. Let vendors compete fairly because they could finally see the playing field.
But here's what separates a marketplace that works from one that becomes corporate software nobody uses: you have to understand how people actually work before you build for how you want them to work.
1. Discovery as the Real Work
Suitmedia started not with wireframes or databases, but with questions. We spent a month interviewing everyone: supply chain managers, project teams, finance controllers, vendors, even general managers.
The goal was simple: put ourselves in their shoes before we designed anything.
What emerged was more complex than a simple "buyer-seller" dynamic. Adhi Karya's procurement wasn't just about transactions. It was regulated. Every approval had to follow company policy. Every vendor payment required documentation. Every purchase was an audit trail waiting to happen.
The marketplace couldn't just be slick; it had to be compliant and fast.
2. Mapping the Real Workflow
We documented this complexity in detailed activity diagrams—not to look impressive, but to make sure we didn't miss a single workflow. We mapped what happened at each step: Who approves? When? Based on what criteria? What documents do vendors need? Where do they attach them?
We asked the uncomfortable questions: Where do approvals break down today? Why?
Every answer went into weekly reports. Every report triggered stakeholder reviews and refinements.
3. From Discovery to Blueprint
After a month of iteration, we produced the Business Requirement Document—the BRD. This wasn't a theoretical artifact. It was the operational bible for the build team.
It said: "Here's how people work. Here's how the system needs to work. Here's where they meet."
The BRD was specific. Not "vendors should be able to upload documents." But "vendors must upload tax registration, bank details, and proof of insurance before they can receive payment, and the system must validate these documents against a checklist before flagging them as complete."
Not "project teams should see prices." But "project teams see prices only after they've been approved by finance, and the system logs this approval with a timestamp and user ID for audit."
4. Why Specificity Matters
Why does this level of detail matter? Because without it, the build team makes assumptions. And assumptions in procurement systems create compliance gaps or worse—they build features that nobody actually uses because they don't match real workflows.
The one-month discovery phase wasn't overhead. It compressed months of rework.
5. The Bridge Between Discovery and Build
When the development team started building in 2019, they weren't guessing. They were executing against a shared understanding of what success looked like.
Did the BRD hold perfectly once we started building? No. As developers began coding, edge cases emerged. Vendors asked for features we hadn't anticipated. Project teams found workarounds that revealed we'd misunderstood a workflow.
But because we had a solid foundation, changes happened within a framework, not in chaos. The marketplace went from theory to live platform, not because the plan was perfect, but because the plan was real.
From Launch to Living System
When the marketplace went live, something shifted in how people worked.
1. Vendors Became Visible
For the first time, vendors could see all the materials they'd sold to Adhi Karya listed in one place. They could compare their pricing against others—not perfectly, because competitive products aren't identical, but enough to understand where they stood.
Some vendors immediately started optimizing their offerings. Others realized they were overpriced and adjusted.
Competition became visible and healthy, rather than opaque and frustrating.
2. The Anxiety Disappeared
Vendors stopped wondering if their bid had been received or reviewed. They could log in, see their active quotes, track approval status in real time, and attach documents directly.
The anxiety of "did they get my email?" evaporated. The marketplace forced clarity.
3. Project Teams Moved Faster
Project managers could now submit requests and see available options immediately. Instead of calling three vendors and waiting for callbacks, they could compare quotes in an afternoon.
Approvals that used to live in email chains now had a defined path: submitted, reviewed, approved or rejected. A project team could see exactly where a request was stuck.
Cycle times compressed—not because the system was magic, but because friction points were visible and deliberate, rather than lost in organizational fog.
4. Finance Got Their First Real View
For the first time, finance could see what was being bought, by whom, at what price, and when it was approved. They could spot trends: Which vendors were overpriced? Which material categories had cost drift? Where were approvals bottlenecking?
This visibility wasn't theoretical. It meant finance could have real conversations with project teams and vendors about cost optimization, backed by data.
5. Compliance Stopped Being Manual
Every approval had a timestamp and a user ID. Every vendor payment required attached documentation. Audit trails were automatic.
Compliance went from "hope someone kept those emails" to "the system has records."
6. The Deeper Shift
The real outcome wasn't revenue or cost savings—those take time to quantify and depend on operational discipline. The real outcome was that procurement stopped being invisible.
When things are invisible, people treat them as inevitable bottlenecks. When they're visible, they become manageable.
What Actually Changed
1. Stakeholder Alignment Precedes Technology
The month we spent understanding how Adhi Karya actually worked wasn't nice-to-have research. It was the prerequisite for a system that would actually be used.
When you skip this—when you build a marketplace that looks good but doesn't match how people work—adoption fails silently. People don't use it because it solves problems they don't have the way they don't experience them.
The discovery phase was the real value. The technology just made it enforceable.
2. Procurement is Organizational Change, Not Just Software
We expected the hard part to be technical: building a scalable platform, integrating with payment systems, managing inventory data.
The hard part was actually organizational: helping people unlearn email-based approval workflows, getting vendors to upload documents instead of calling, convincing finance that they needed to review spending data instead of just processing invoices.
Technology enables change, but it doesn't cause it.
3. Change Happens When New Ways Are Easier
Change happens when the system makes the new way easier than the old way, and when people understand why the new way matters.
For Adhi Karya's vendors, the marketplace wasn't a burden because it let them see their competitive position and upload documents once instead of chasing emails. For project teams, it was faster than calling.
The technology succeeded because it aligned with what people already wanted—speed, clarity, and fair competition.
4. Digital Platforms Are Trust Infrastructure
A marketplace is only valuable if all participants trust it. Vendors need to trust that their pricing won't be used against them unfairly. Project teams need to trust that approvals will happen fairly and on time. Finance needs to trust that the data is accurate.
Building that trust meant the system had to be transparent, fair, and consistent. It meant no hidden rules or arbitrary decisions.
Once that trust exists, the platform becomes self-reinforcing. People use it because it works, and it works because people use it properly.
Strategic Insights for the C-Suite
1. Procurement Is Often Your Biggest Untapped Leverage Point
Most companies treat procurement as a cost center to optimize, not a strategic asset to build. Adhi Karya realized that their vendor relationships and purchasing velocity directly enabled project delivery.
By making procurement visible and fair, they didn't just reduce friction—they made vendors want to compete harder and project teams more confident in their planning.
Procurement transformation often delivers faster ROI than sexier initiatives because you're removing friction that already costs you every single day.
2. Discovery Work Compresses Implementation Risk More Than Most Leaders Realize
The instinct in large organizations is to move fast—skip the research, get to the build. But in complex systems like procurement, the cost of building the wrong thing is steep.
One month of disciplined discovery with key stakeholders prevented months of rework. The BRD wasn't a deliverable we handed off; it was shared understanding that guided every build decision.
Invest in discovery rigor proportional to complexity and interdependence, not just timeline pressure.
3. Visibility Is Often More Valuable Than Optimization
Adhi Karya's biggest win wasn't cost savings—though those will follow. It was making procurement transparent.
When you can see what's happening, you can manage it. When it's invisible, you're hostage to it.
Build systems that illuminate before you build systems that optimize. Optimization follows naturally once people understand what's actually happening.
4. Trust in Digital Systems Is Structural, Not Assumed
A marketplace only works if all parties trust the rules are fair and consistent. This means the system itself has to enforce transparency and eliminate arbitrary decisions.
Adhi Karya's vendors adopted the platform because they could see pricing comparisons and approval workflows. Finance trusted the data because audit trails were automatic.
Trust isn't soft; it's built into how the system works.
