About
We would rather be corrected in public than believed by accident.
MyClient.software is a Stanley Studios product. This page is not a company story — there is no founding myth and no team roster here, because neither would tell you anything you could check.
What follows is the rule this site is written to, the two times our own code told us the wrong answer, and the reason this is a separate product at all.
Why this is a separate product
An object model is an argument, so it deserves its own front door.
A data model is a claim about which things exist, which of them are the same kind of thing, and what is allowed to happen between them. Once it ships, everyone who uses the software has to believe that claim in order to get through the day. The general-purpose CRM makes a coherent one — companies, employees, purchase orders — and it is right often enough to have built an enormous category.
Selling into a school district is the case it is wrong about, and not marginally. That is a big enough disagreement to be its own product rather than a configuration of somebody else’s, which is why this exists as its own thing with its own front door.
The same reasoning is why the neighbouring products are kept apart rather than folded into a suite. Money out to staff is not money in from a sale; a signed contract becoming a date on a calendar is a different job from winning the contract. Each of those is its own product with its own model, and a suite that blurred them would be making a claim about the world we do not believe.
How this site is written
Every claim names a file, and where the rule is load-bearing, a line in it.
The characteristic dishonesty of a technical product page is to present a green test suite as a working feature. It is not usually a lie; it is a claim with the scope quietly removed — true of the code, untrue of anything a customer can open. So this site works to one rule: a capability is described as reachable only when a registered handler serves it and a screen you can reach from the navigation calls it. Everything else is named as what it is.
That rule produced the strangest page on this site, and we kept it. The built-not-switched-on table lists capabilities that are written, registered, and called by nothing a person can open. It is the section we would delete if we were selling harder, and it is the reason to believe the rest.
It also produced the measurement discipline you will see repeated: every count on this site states the instrument that produced it, and where a count is zero, the same instrument is shown returning a non-zero result somewhere else — so a zero is provably an absence rather than a search that was silently broken. The what you can reach page is where that is done most carefully, because that is the page with the most to lose from a lazy zero.
What happens when we are wrong
Our own source code told us the wrong answer, and we published that.
Two comments in this codebase assert that the deal detail screen is reached from the pipeline and the deal cards. It is not. We found that by searching the whole web application for the route literal and for a navigation call, and finding only the route declaration, those two comments, and the page’s own header. The comments were the thing telling us the wrong answer — which is the entire reason this site cites a file and a line rather than quoting a comment.
The second case is a claim of ours that stopped being true. This site used to carry a row for a drag-and-drop deal board that was fully orphaned: no route, no navigation entry, and the only caller of the deal-list endpoint. That is no longer the case — the board is now mounted at a real route with a navigation entry, so a person can open it. We removed the row because it became false, and we left the paragraph saying it had been there.
Two further rows changed the same way and say so in their own third column: account writes and the district roll-up both used to read “no browser client at all,” and both now have a client with no caller. Still unreachable — but by a different measurement than the one we first published, and the difference is stated rather than smoothed over.
The general rule: a claim that quietly disappears is worth less than one that is corrected out loud. Corrections in the less flattering direction are the ones nobody checks, which is exactly why they are the ones worth publishing.
Who makes it
MyClient.software is a Stanley Studios product.
It is built and operated by Stanley Studios, and it is early access: one lane — advertising and sponsorship sales — is wired end to end and reachable from two navigation entries, and the rest of the model is written with its gaps named on this site rather than discovered in week three.
What we are deliberately not telling you here is as load-bearing as what we are. There is no customer count on this site, no named district, no testimonial and no adoption figure, because we do not have ones we could state with an instrument attached. There is no pricing and no checkout either: the live payments switch defaults off, and the only settlement this system can record today is an attested offline reconciliation. The what it refuses page describes exactly what that means.
The honest next step is a conversation rather than a signup. If you want something on this site measured, ask — the answers are more interesting when they are specific.