Data & IP
What access is asked for, and who owns what
Handing an outside party access to your go-to-market systems is a real decision. This page sets out how access is scoped, what will never be asked for, and how ownership is divided - so it is agreed in advance rather than argued afterwards.
Access is staged
Access is requested for the stage of work actually underway, not for the engagement as a whole. An audit needs to understand how the motion runs; it does not need production credentials. A build needs more, and only then.
In practice that means each stage starts with a conversation about the narrowest access that lets the work proceed, and access granted for an earlier stage is not assumed to carry into a later one.
What will not be requested
If any of these comes up, it is reasonable to push back and ask why.
- Credentials for systems the work does not touch
- Admin or unrestricted access where scoped access does the job
- Customer data that is not needed to answer the question in front of us
- Access that outlives the stage of work it was granted for
Retention
There is no formal retention policy in place today. Rather than publish a number that nothing currently enforces, here is the actual position: material shared during an engagement is held for as long as the work requires it, and can be deleted on request at any point.
If you need a defined retention period, say so before work starts and it goes in the engagement schedule as a commitment rather than an assumption.
Ownership, in three categories
The short version: what gets built for you is yours, the engine it runs on is licensed to you, and no client-specific information ever leaves with it. The boundary is put in writing before build work starts.
What gets built for you
The ICP schema built for your market, your qualification and scoring logic, prompts tuned to your buyers' language, research outputs and account files compiled from your list, workflow documentation, and evaluation results run against your accounts. These vest in you on payment.
Amoris pre-existing IP
The engine and the methodology that existed before your engagement began: the pipeline architecture, the early-stop design, the evidence-traceability rules, and the outbound methodology behind them. Anything deployed to you comes with a perpetual, irrevocable, royalty-free licence for your internal use. You can keep running it indefinitely. You do not acquire ownership of it.
Methodology and learning
Working on your problem sharpens how the work is done. That generalised improvement travels to later engagements. Nothing confidential, nothing client-specific, and nothing identifying ever travels with it.
Questions before you share anything
Reasonable to want this settled before an engagement rather than during one. The intro call is free, and this is a fair thing to spend it on.