Contact · MyClient.software
Bring one adult organisation relationship and the next decision you need to make.
MyClient.software is early access. The useful first conversation is not a tour of a generic CRM; it is a careful account of one organisation, the adults connected to it, the deal in progress, and the action that should happen next.
Email [email protected]. This page has no contact form, creates no account, starts no sequence, and promises no delivery or response time. The link asks your own email application to compose a message; your provider controls transmission.
What to include
Describe the organisation, the people, the deal, and the next action as four separate things.
Start with the organisation that acts as the account. In the current school-studio expression, that account is a school joined to its directory row, and the district above it is resolved from the directory rather than typed as a second account. For another adult business relationship, describe the equivalent organisation and any parent relationship you need to see. A synthetic name is enough for an early conversation.
Then name the adult contact roles involved. One account can have several people because the person who uses a service, the person who signs, and the business office that documents settlement may be different adults. Say which role matters for the case and which person owns the next conversation. Do not paste a contact export, credentials, private correspondence, or identifiable records into an introductory email.
Describe the deal as a proposed commercial relationship, not as a colored row. Include its current stage, expected close period, amount shape, owner, and any line-item or catalog dependency that changes the decision. If the case is about a proposal or insertion order, name its actual status and the transition you expected. The server enforces legal transition ladders; it does not permit a client to overwrite status freely.
Finally, state the next action. It may be a call, a task, a document review, a stage decision, or investigation of a refusal. Include the responsible adult, the useful due date, and what fact would make the action complete. That gives the conversation an operational test instead of a list of features.
What we can discuss honestly
A registered handler, a reachable screen, and a daily workflow are three different claims.
The advertising and sponsorship sales lane is wired end to end and reachable from navigation. The general deal, forecast, account, and territory work is less even. Some reads are reachable, the deal detail that owns the full write path is reachable only by typing its URL, and some registered endpoints have no browser surface at all. Account creation and editing do not have a browser screen. A useful reply will name the exact rung instead of calling every compiled endpoint a feature.
The contact model and activity timeline are reachable from prospect work. A stage move writes an activity and updates the last-activity clock, which gives the quiet-deal rule a real event to read. The forecast derives expected revenue from open-deal integer cents and integer basis points, stores no forecast total, excludes closed deals, and skips a deal with no stage rather than inventing a probability. Those are source-grounded capabilities we can walk through.
The account read joins directory context, the deal, and a provisioned customer when those links exist. Missing links return as missing; the read does not fabricate an organisation state. District roll-up also re-checks the linked deal’s tenant before trusting its amount. Support may read across tenants for support work and is refused every write. A rep is limited to owned or worked deals plus the unassigned house pipeline.
Status is not outcome
Tell us whether you need a label changed or a real-world event established.
A stage records where an open deal sits in a studio’s process. It is useful for work allocation and forecasting, but it cannot prove that a contract was signed, a customer was provisioned, a document was issued, or money arrived. Those outcomes have their own verbs and evidence. In the advertising lane, a proposal must move through its allowed ladder; an insertion order must be signed before creative can attach.
Conversion is a consequential outcome. The convert verb provisions the customer workspace, and the deal becomes immutable afterward. It cannot be dragged back to negotiation as if the created customer never existed. When you write, say whether your problem is stage design, a refused transition, conversion, next-action ownership, or reporting. The distinction often determines whether the needed path exists.
Money and automation boundaries
No checkout, provider charge, email sequence, or AI sales agent is hiding behind this address.
The live-payments switch defaults off. With it off, a live provider key is held rather than used. The reachable settlement path records an attested offline event with a method, a reference, and the staff member resolved by the server. That record documents what an authorised adult says happened elsewhere; MyClient does not move the money and does not convert the record into proof of a provider charge.
There is a cadence data spine and a pure step resolver, but there is no endpoint that runs a sequence, no screen that builds one, and nothing that sends a cadence message. There is no AI assistant that writes outreach, chooses the next action, changes a stage, scores a deal, or answers this mailbox. Forecast and lead-score outputs are deterministic rules with named integer inputs, not model recommendations.
If live billing, automatic outreach, or an AI agent is essential to your present workflow, include that requirement. The honest answer may be that a general CRM covers it today and MyClient does not. Early access is a fit review, not a promise to re-label an absent engine.
Write when the case is ready
One synthetic account is enough for a useful first exchange.
Use invented organisation and adult-contact names, then include the current status, desired outcome, next action, and the source document or rule that governs the decision. Email [email protected]. The address is a contact route, not a support guarantee: this site does not assert that a mailbox is continuously monitored, that a message was delivered, or that a reply will arrive within a stated window.