What we’re building.

What it takes

1. 01Build the panel that reaches the service. The service, its limits and its tests are already on main; nothing calls them.
2. 02Put the attachment control in the composer as well, because below 1280px the side panel is a closed overlay.
3. 03Ship the two disclosures the record requires: what the scope is used for, and that an approved one cannot be withdrawn.
4. 04Name the file in our own copy beside the error, never inside it -- a file called 'Sign in sheet.pdf' once matched a rule and came back as an authentication failure.

What it takes

1. 01Promote it from a template to a tailored pack, the way construction was.
2. 02Bring across what the Synergy operations console already learned about counts, waste and supplier invoices.
3. 03Validate against an operator who is not the one we already work with.

What it takes

1. 01Promote it from a template to a tailored pack.
2. 02Model utilisation, engagements and handoffs -- the three things every firm of this shape argues about.
3. 03Validate with a firm that bills time, not deliverables.

What it takes

1. 01Add a diagnostic setting to the model accounts first, so a request body is recoverable after the fact. A past incident could not be explained because nothing logged it.
2. 02Build queries in code from the customer's own words. The model never composes the search string, so it cannot put the transcript into one.
3. 03Off by default, chosen per turn, never remembered. Absence of the tool in the request, not a flag the service interprets.
4. 04Strip live links and bare URLs before anything reaches a document a human opens.
5. 05Three independent switches, including one at the subscription level that does not depend on our code being correct.

What it takes

1. 01Show the customer the exact redacted text before it leaves, not a summary of it.
2. 02Say plainly, on the screen where they approve, that an approved scope cannot be withdrawn.
3. 03Keep the two destinations separate in code, so asking for an engineer can never contribute knowledge by accident.
4. 04Accept the record. It is proposed and its author cannot accept it.

What it takes

1. 01Decide what a unit is: a plan, a seat, or a month. Nothing else can be designed before that.
2. 02Take payment on a hosted checkout so card data never touches our infrastructure.
3. 03Connect the entitlement checks that already exist to a paid state, rather than building a second concept of access.
4. 04Write the cancellation, refund and failed-payment behaviour before the first charge, not after the first complaint.

What it takes

1. 01Microsoft Entra first: most businesses we talk to already have it and are already paying for it.
2. 02Map groups to roles, so access ends when someone leaves the company rather than when we remember.
3. 03Automatic provisioning after sign-in works, not at the same time -- the two fail differently and debugging both at once is how you ship neither.
4. 04Keep named invitation as a fallback for businesses with no identity provider at all.

What it takes

1. 01Split extracted text into passages that keep a stable pointer back to document, page and position.
2. 02Provision an embedding model and an index inside the tenant that already holds the documents. No new place for customer data to live.
3. 03Retrieve per turn and pass only the passages that matter, instead of the whole document -- which is also what makes it work past the extraction character cap.
4. 04Render each claim against the passage it came from, so a number in a plan can be clicked back to the line it was read from.
5. 05Score it on wrong citations, not just missing ones. A confident citation to the wrong paragraph is worse than none.

What it takes

1. 01Define the specification as a schema -- tasks, systems, owners, dependencies, assumptions -- with fixtures that must fail.
2. 02Constrain the model to emit that shape, rather than generating prose and parsing it afterwards.
3. 03Keep the readable document as a rendering of the same object, so there is one source of truth and not two.
4. 04Version the schema on day one, so a plan written today still opens in a year.

What it takes

1. 01Approval first: the email that says your workspace is open, with the link to it.
2. 02Then reviewer replies, which is the one people are actually waiting on.
3. 03Send from an address that accepts a reply, because people will reply to it.
4. 04One switch to stop them, honoured everywhere, before the first send.

What it takes

1. 01Name the artifacts a project actually runs on: submittals, RFIs, schedule of values, punch list.
2. 02Write the vocabulary and the workflow stages as their own pack, separate from the company-level one.
3. 03Validate with a builder running several jobs at once, before writing more of it.
4. 04Keep the packs independent, so a firm can use company management, project management, or both.

What it takes

1. 01Decide first whether this is its own domain or a specialty inside construction. Getting that wrong costs a rewrite.
2. 02Dispatch, route and parts vocabulary, which is where it genuinely differs from contracting.
3. 03Validate with a service company that dispatches daily.

What it takes

1. 01Adopt the open connector standard both major vendors now use. Inventing a private one is a cost with no upside.
2. 02Unblock the SharePoint connector our own register already lists as declared and blocked.
3. 03Read-only first. No connector writes to a customer's system until a separate decision says it may.
4. 04Per-connector consent, and a record the customer can read of exactly which records were pulled into a conversation.
5. 05Settle credential custody, rotation and revocation before accepting a single customer token.

What it takes

1. 01Decide what may be remembered -- systems, vocabulary, constraints -- and what never is. This is a decision, not code.
2. 02Show it back as a list the customer can read. Memory nobody can inspect is a liability rather than a feature.
3. 03Correction and deletion in plain language, where deleting actually removes it rather than hiding it.
4. 04Scope memory to the business, not the individual, so it does not leave when an employee does.
5. 05Only then use it in a conversation.

What it takes

1. 01Accept images through the same guarded upload path documents already use, rather than a second one.
2. 02Extend the content filter to text inside an image, or keep refusing images until it does. A photo of a password is a password.
3. 03Send an image only on a turn the customer chose to send it on.
4. 04Separate what was read from a photo from what was inferred about it, the same way the plan separates confirmed from assumed.

What it takes

1. 01Version the surface and publish the contract. Today it is shaped for our own workspace and unversioned.
2. 02Authentication that is not a workspace session, with per-customer scope.
3. 03Rate limits and quotas, so one caller cannot spend another's capacity.
4. 04A written deprecation policy before the first outside caller depends on it. That commitment is the real cost, not the endpoint.

What it takes

1. 01Collect real planning problems with known outcomes, with the customer's consent, rather than inventing test cases that flatter us.
2. 02Score whether assumptions were surfaced and whether the plan was actionable -- not whether the prose reads well.
3. 03Re-run on every model change and publish the difference, including where it got worse.
4. 04Publish the failures next to the passes, or the number means nothing.

What it takes

1. 01One format done properly first, rather than three done badly.
2. 02Carry the confirmed-versus-assumed marking into the export. A plan that loses it on the way out is a more dangerous document than the original.
3. 03Static export means no server-side rendering, so the file is built in the browser.

What it takes

1. 01Decide what a workspace belongs to -- a business, not a person -- because everything else follows from that.
2. 02Roles that match how these businesses run: someone who decides, someone who does the work, someone external who advises.
3. 03Removal that actually removes, including from plans already in flight.
4. 04This is the same decision as memory scope and sign-on scope. Deciding all three at once is cheaper than three times separately.

What it takes

1. 01Store versions before building any interface, because the interface can be added later and lost history cannot.
2. 02Show a difference between two versions, not a list of timestamps nobody can read.
3. 03Depends on more than one person being in the workspace to be worth much.

What it takes

1. 01Find every place a customer's content lands, including the ones that are not the obvious store.
2. 02Decide what an approved contributed scope means here, since the record says it cannot be withdrawn. Those two commitments have to be reconciled in writing before either is promised again.
3. 03Produce a record of the deletion that outlives the data.

What it takes

1. 01Decide what a customer-visible event is. Our internal ledger is far too granular to hand over and would be unreadable.
2. 02Separate their events from ours rather than filtering one stream into the other.
3. 03Export, because an audit log you cannot get out of the product is not evidence.