How to Position a ConTech Product Against the Incumbents

Almost every ConTech founder we meet makes the same early mistake. They build a feature comparison table with themselves on the right and Procore, Aconex or Viewpoint on the left. Green ticks down their column, red crosses down the incumbent's. Then they wonder why the deck doesn't close meetings.

Two problems. First, the commercial director you are pitching already pays for the incumbent and has for six years. If your deck says the product they bought is rubbish, you are telling them they made a bad decision. They didn't — the incumbent is genuinely good at most of what it does. Second, you cannot actually out-feature a platform with 800 engineers and a 15-year head start. Every buyer knows it.

The winning move is the opposite. Concede the incumbent is excellent. Then identify the one job they do badly, and position there. "Procore is the best common data environment in the industry. But if you want real-time subcontractor RAMS flowing from site to head office, Procore was never built for it. We were." That is a positioning a buyer can repeat internally without losing face.

Not every gap is worth a product. Good positioning gaps share three traits:

1. The incumbent cannot close it quickly. If the gap is a roadmap feature, they'll ship it in two quarters and you'll lose. Pick a gap rooted in architectural decisions — single-tenant vs multi-tenant, desktop vs mobile, structured vs unstructured data.
2. The pain is quantifiable in hours or pounds. "Better UI" is not a gap. "9-day RFI cycle dropped to 2 days" is a gap.
3. At least one role in the buying committee feels the pain weekly. If the pain is abstract or annual, procurement will never approve the line item.

A useful exercise: sit on site for a week with a PM. Note every time they swear at software. Count the frequency and stopwatch the time lost. The three most expensive recurring pains are your positioning shortlist.

In construction SaaS, price communicates positioning as clearly as the deck does. There are three bands:

• Below £20 per user per month — you are a utility, a spreadsheet replacement. Reads as indie / consumer-grade. Hard to sell to Tier 1.
• £49-£299 per user per month — you are a specialist tool. Priced seriously but not suite-scale. This is the winning band for almost every modern ConTech company.
• Enterprise seat / platform pricing (£50k+ annual) — you are a suite. You need a 15-person sales team and a 12-month sales cycle.

Most early ConTech founders underprice. They set seats at £15 per month, trying to look accessible, and end up signalling that the product is a toy. We have seen clients raise from £15 to £89 per user per month, rewrite their LinkedIn positioning to match, and book more deals, not fewer, because commercial directors stopped filing them in the "indie tool" mental bucket.

There is a cultural taboo in SaaS about not naming competitors. Ignore it. In construction ConTech, comparison content is the highest-converting content you can publish.

Why: the commercial director evaluating your product is also evaluating two other products. They are typing "[your tool] vs Aconex" into Google. If your LinkedIn and site content don't answer that query with a grown-up, specific comparison, someone else's blog will. Probably the incumbent's.

Structure a comparison post like this:

1. Start with genuine praise for the incumbent's strengths. Builds credibility.
2. Name the two or three jobs they do less well, with specifics.
3. Describe what you built differently and why it matters for a specific workflow.
4. Close with "if your main job is X, they are the better choice. If your main job is Y, try us."

A commercial director who reads that comes away thinking you are a serious, honest operator. That is worth more than any feature advantage.

One under-used positioning angle: implementation time. Procore implementations on a mid-size contractor typically run 6-9 months including data migration, training, and phased rollout. Aconex on a large programme can be 12+ months. The buying committee has seen this film before.

If you can honestly promise a four-week pilot on one live project with real data flowing by week two, that is not just a feature — it is a wedge into the organisation. The commercial director does not have to commit the whole estate. They let you onto one £18m school rebuild, you prove the numbers in a month, and the expansion conversation writes itself.

On LinkedIn this translates into content like: "Here's what week one looks like on a live NEC3 job" with actual screenshots. That content disproportionately outperforms generic benefit posts because it answers the procurement question every buyer is holding in their head.

If you win enough deals, the incumbent will notice. They will send their enterprise account director to your target's office with a discount, a roadmap slide, and a lunch. You cannot out-spend them on that day.

Your defence is the depth of relationship with the operational team. If the PMs and planners genuinely prefer your tool — because it saves them an hour a day — they will push back internally even when the commercial director is being wined. That is the real reason we insist on targeting PMs first, not CTOs. PMs are the moat.

So what: Position narrow, price serious, name names, and implement fast. That is a coherent posture that wins against incumbents ten times your size — because you are not actually competing with them, you are competing for the one job they do badly.