Software as a service platform development
in Sunnyvale

Every online service eventually gets integrators. People at a customer company who need to connect it to a CRM, a data warehouse, or some internal tool built years ago. What they find when they arrive decides whether the connection takes an afternoon or turns into a support ticket that repeats every few months.

A page of prose describing endpoints is not documentation. Working documentation shows a real request, a real response, and the exact error a person will hit if a field is missing or a type is wrong. A working sample beats a paragraph of description every time.

Authentication deserves its own page, written for someone who has never seen the system before. Which key goes in a header. Which one goes in a query string. What a token looks like when it expires, and what the platform returns in that exact case. Skipping this step pushes the same three questions into a support inbox, week after week.

Versioning is where documentation quietly goes stale. A field gets renamed, a response shape changes, and someone updates the code without updating the page describing it. A changelog attached to the documentation, dated and specific about what broke and what did not, saves an integrator from finding out through a failed request in production.

Retiring an old endpoint deserves a firm, published policy rather than a surprise. A marked retirement date, set months ahead and listed next to the endpoint it replaces, is what lets an integrator plan a release around it instead of scrambling once a request suddenly starts failing.

Code samples matter more than most teams budget for. One language is a start. Three or four common ones, each tested and kept current, cover most of the integrators who will ever show up. A sample that no longer runs is worse than no sample, because it wastes an hour before anyone realises the code itself is the problem.

None of this needs to launch on day one. A small platform with a handful of customers can survive on a shared document and a direct line to an engineer. Past a certain number of integrators, that document becomes the bottleneck, and a proper portal starts paying for itself in support hours saved.

Some platforms are sold once, directly, to the person who logs in every day. Others take a second path. A second business resells the platform under a different name to its own customers. That pattern changes what the software has to support: a login screen, an email footer, and a dashboard that can wear a logo belonging to someone else.

A custom domain is the visible half of this. Instead of an address that names the underlying platform, the reseller points its own domain at the same application. The platform then serves the right branding, certificate, and content for whichever domain the request arrived on. Each domain should renew on its own schedule. No manual attention. That is what breaks first if it was rushed.

The second half is everything a user actually sees. A logo is the easy part. Harder is every email the system sends in the name of the account: a password reset, a receipt, a weekly summary. If those still carry the name of the underlying platform, the reseller relationship becomes obvious at the worst possible moment, usually when a shared customer opens their inbox.

Support pages and help text carry the same risk. A tooltip says to contact one company. The invoice comes from another. That confuses the very people the reseller is trying to keep. Every piece of customer-facing text needs a variable in place of a hardcoded name.

Pricing and permissions add a layer most teams underestimate. A reseller usually needs its own plans, its own limits, and its own support tier for each of its customers, separate from whatever the underlying platform offers directly. That layer sits above the normal account settings, visible only to the reseller, never to the end customer.

None of this needs to exist from day one. Plenty of platforms launch and prove their value with a single shared domain and a single visible brand. That is fine at first. A platform planning to grow through resellers benefits from designing the domain and branding layer early. Retrofitting it later costs far more than building it in from the start.