9 Go-to-market

Start with developers and businesses not yet committed to a platform. Help their agents read the docs and integrate successfully, then grow through use, referrals, and partner shares.

Praxis starts with existing users, executable documentation, and partners to serve developers and businesses that are not yet deeply committed to another platform.

Who comes first

We start with creators, independent developers, and small teams in Chinese-speaking markets in China and Southeast Asia. We first serve those needing an affordable option who have not tied their work to one runtime, rather than actively pursuing deeply committed customers.

The sequence is existing Praxis App users, developers arriving through documentation, and businesses introduced by partners. We validate the approach in one market before taking reusable methods to another.

Stage	What customers are doing	What the platform must provide	Measure
Resource access	Try the first call	Connect by adjusting settings within supported scope	Time from sign-up to first successful request
Continued use	Handle daily tasks and errors	Common credentials and clear error recovery	Number of keys to manage; self-service recovery rate
Service building	Move from use to building and publishing	Build a service through conversation and feedback	Use-to-build and build-to-publish conversion rates
Referrals and partnerships	Help other businesses connect	Referral rewards, distribution shares, and partner cooperation	Share of resource usage brought by partners

A conversion rate is the proportion of people who move from one step to the next. Each stage has its own measure; registration counts do not tell the whole story.

Documentation is an entry point

A shop owner may ask their agent to “add customer support to my website” before studying our homepage. An agent reads information, uses tools, and performs tasks for a person; it will use the docs to judge whether Praxis can do the job and then integrate it for the owner.

This is documentation as a control plane: instructions through which agents operate the platform, beyond a product introduction. In this form of integration, the first reader is an agent. Customer acquisition for a supply-side platform therefore shifts from the homepage to the docs; readable, executable documentation makes successful integration possible.

The docs must bring together prerequisites, integration steps, expected results, and recovery instructions. Compatible resource services let customers adjust connection settings from their own environment without first moving the entire agent or learning the whole system; supported interfaces and specific addresses are in the developer documentation.

Successful integration gives customers a reason to stay

For the shop, success means support is working on its website, not that an agent has read many pages. Each unclear step adds another chance of failure; retention depends on whether an agent can complete a short enough path successfully on the first attempt.

A common address and API key reduce connection information to manage, while errors must explain the cause and next action. Incorrect docs can lead agents to repeat mistakes and can be collected and spread elsewhere, so documentation accuracy directly affects product usability.

From use to operating a service

The owner first uses agents in Praxis App, then builds a service with their own information and rules, and publishes a tested version for customers. Work creates a reason for each step from user to builder to service publisher.

The App should balance professional depth and ease of use; Personal Agents handle building, integration, and operations within it. This serves business production rather than turning Personal Agents into another mass-market personal entry point.

Customers and partners bring customers

Owners can refer other businesses, and developers can become partners who help businesses integrate. Referrals receive rewards, distribution earns a share, and referrers can keep introducing customers; customers, partners, distributors, and resellers participate through the same system.

We share some proceeds with those who bring actual usage, replacing an advertising budget and an ever-growing sales force. The next chapter describes who builds these processes and how the team works.