Enterprise software automation Evidence brief

Conduct GTM Unpacked. How did Conduct grow?

Deployment roles match the complexity of enterprise systems

Conduct go-to-market evidence brief. Conduct’s current team page emphasizes enterprise software and S/4HANA migration, and links an SAP partnership. [1]

Human Led Partner Led Enterprise software automation

[Inference] Motion labels describe routes across segments and periods, not measured revenue shares. Acquisition channels and operating patterns are shown separately in the case.

1 linked source Published by GTM Unpacked Research date · Add to comparison
Reading this case

Source numbers link to evidence. [Inference] marks analytical judgment, including motion classifications and causal explanations. Public evidence does not establish every internal decision or metric.

Conceptual technical plate for Conduct, showing a gear, stacked panels, and a checklist sheet in a staggered composition.
ILLUSTRATIVE PRODUCT PLATE

Conceptual illustration of interlocking machinery, layered panels, and a checklist, describing enterprise-software complexity through objects rather than presenting a verified deployment architecture.

Company
Conduct · Enterprise software automation · conduct.ai
Conversion motions
[Inference] This research classifies Conduct as Human Led and Partner Led.
Conduct beachhead and target customer
[Inference] Enterprises modernizing and operating complex business systems.
Product and buying complexity
[Inference] Legacy architecture, business-process ownership, migration risk and procurement complicate the decision.
Market at entry
[Unverified] This focused brief does not establish the full market conditions at first sale.
Evidence
Evidence brief · 1 linked source · research date · method and limitations
The ten-step Revenue Engine reading map

These links locate relevant evidence. A linked section does not imply every detail of the step is publicly established.

  1. Acquire Your First Customers: Founder Led Sales Read first customers
  2. Embrace GTM Experimentation Read experiments & lessons
  3. Understand Your GTM Motion Options Read GTM motion
  4. Pick Your GTM Motion Not established in this entry
  5. Generate a Lead Read GTM motion · Read experiments & lessons
  6. Turn Leads into Paying Customers Read GTM motion
  7. Retain and Grow Your Customers Read retain & expand
  8. Build Your GTM Team Not established in this entry
  9. Plan Your Tech Stack Read experiments & lessons
  10. Optimize and Scale Through Metrics Not established in this entry
REVENUE ENGINE / STEP 01

Conduct: Origin and evidence boundary

The first paid customer and founder closing sequence were not established in this focused evidence brief.

Conduct’s current team page emphasizes enterprise software and S/4HANA migration, and links an SAP partnership. It lists enterprise account executive and deployment strategist roles in London and New York, alongside ABAP and product engineers. A team testimonial describes engineers owning a customer problem through production. Philipp is identified as co-founder, without a surname in the inspected page. [1]

[1]
REVENUE ENGINE / STEP 03

Conduct: Motion and buyer logic

[Inference] Enterprises modernizing and operating complex business systems.

[Inference] Legacy architecture, business-process ownership, migration risk and procurement complicate the decision.

[1]
REVENUE ENGINE / STEP 07

Conduct: Retention and expansion hypothesis

[Inference] Additional systems and business workflows can widen deployment after a bounded project succeeds.

[Unverified] Individual CSM ownership, enablement conversion and renewal cohorts were not established in this brief.

REVENUE ENGINE / STEP 02

Conduct: Critical reading

[Inference] Pairing commercial and deployment roles fits a complex sale. Track time to production and repeatable delivery effort to avoid treating consulting-heavy work as frictionless software.

[Unverified] The inspected material does not establish failed-channel experiments or a complete causal account of growth.

Conduct economics at a glance: Pricing is only half the story.

Conduct pricing

Exact current pricing was not verified in this brief.

Model

[Inference] Additional systems and business workflows can widen deployment after a bounded project succeeds.

Constraints

[Inference] Pairing commercial and deployment roles fits a complex sale. Track time to production and repeatable delivery effort to avoid treating consulting-heavy work as frictionless software.

CAC

Not publicly verified in this brief.

Retention

Not publicly verified in this brief.

[1]

The people in the Conduct GTM story: People & capabilities.

P

Philipp

People identified in the source

Philipp — co-founder; Isabella — deployment strategist; Abubakar — product engineer, as named on the company page.

See the source-backed account above; additional skills and training are not inferred as fact.

[1]

Conduct GTM: critical reading and analysis: Why it worked.
Where it breaks.

What worked—and why

[Inference] Pairing commercial and deployment roles fits a complex sale. Track time to production and repeatable delivery effort to avoid treating consulting-heavy work as frictionless software.

What did not work

No substantiated failed experiment established in the inspected evidence.

What could have been better

[Inference] Validate the proposed growth mechanism with paid conversion, implementation cost and retained customer outcomes.

What another founder can use

[Inference] Additional systems and business workflows can widen deployment after a bounded project succeeds.

Conduct go-to-market FAQ: The questions that matter.

What does this case establish about Conduct?

The inspected source supports the specific product, people or distribution facts in the origin section; a full chronological reconstruction remains incomplete. [1]

Is the full GTM history of Conduct verified?

No. This is a focused evidence brief. The page distinguishes inspected claims from analytical hypotheses and lists the remaining gaps.

Which go-to-market motions is Conduct classified under?

[Inference] This research classifies Conduct as Human Led and Partner Led. Motion labels describe routes across segments and periods, not measured revenue shares.

Conduct sources and open questions: Follow the sources.

  1. Conduct — inspected company evidence Conduct · primary

    Origin, product, team or current commercial route described in the source; narrower claims are attributed in the text.

What remains unverified

Evidence brief rather than a full historical GTM reconstruction.

First contracts, complete hiring sequence, pricing history, CAC and retention require further source verification.

No historical website screenshot or named account expansion is represented as verified.

No verified visual capture is attached to this entry. A current screenshot is not a substitute for a historical capture.