Confidentiality
A mutual NDA is signed before anything sensitive is shared, as standard practice rather than on request.
On a program of any size the supplier conversation stops being about software and starts being about paperwork: who carries the insurance, who owns the data, what happens if the supplier disappears, and who answers the security questionnaire. We bring all of it to the first conversation rather than waiting to be asked in week six.
Assurance and commercial terms
Each one is a commitment written into the engagement rather than a page of marketing.
On confidential work, the people on the engagement are the people named on the agreement. Nothing about the commercial relationship depends on it being difficult to leave. We do not overstate our credentials, and what we hold you can verify. The deployment choice is decided by the work and by your risk position, not by what is convenient for us to host. Procurement material is ready when your team asks for it rather than assembled after a delay.
The answer to what happens if we are unavailable exists in writing. There is no rate card, no hourly billing and no open-ended estimate. A program never drifts quietly and no invoice arrives as a surprise. Every installed system carries an update path from its first release.
Confidentiality
A mutual NDA is signed before anything sensitive is shared, as standard practice rather than on request.
Data ownership
You own your data, in a documented structure, exportable at any time.
Security review
We complete your vendor security questionnaire and work through your review as part of the engagement.
Deployment model
Cloud, private cloud, or on premises inside your own environment.
Procurement
Entity details, tax documentation, certificates of insurance, a master services agreement and references.
Continuity
Documented handover, source available to you where that is the agreement, and escrow where your review requires it.
Commercial structure
One number against a written scope, with payment tied to milestones rather than elapsed time.
Change control
A change to scope is priced and recorded as an amendment that names what it replaces.
Support
Terms written into the agreement, with a named lead who was there from discovery.
Data and claims
Three things decide whether a system is safe to commission, and all three are settled in scope rather than discovered later. For confidential and clinical work, on premises is available and is sometimes the right answer. Who can see what is decided in architecture, because it cannot be retrofitted.
Where more than one organization's data sits in one system, separation is designed in at the start and verified by an automated scan of every query, because a separation failure is the one defect that cannot be apologised for afterwards.
Where the data lives
Named explicitly: your environment, a private cloud, or on premises.
Who can see what
Permissions are enforced on the server rather than hidden in the interface, so a web address cannot reach a record.
What is recorded
Who did what, when, and what changed, kept as history rather than overwritten, and exportable by you.
A supplier that overstates its credentials in a sales conversation is a supplier that will overstate progress later, so it is worth being exact here. If a standard matters to your review, ask directly and you will get a direct answer.
We will complete your security questionnaire
And work through a vendor review, a risk assessment and a procurement process.
We will sign confidentiality agreements
Before technical detail is shared, in either direction.
We will put insurance certificates in front of your team
On request, with the limits your contract requires.
We do not overstate our credentials
In any conversation, document, proposal or page.
Proof
The word done means something specific here, and it is not a status update.
Every check is made to fail on purpose first
So a passing suite means something. A test that cannot fail proves nothing.
A real tap and a real mouse click
Interfaces proven at phone width and desktop width, in a real browser.
A real record out of your live system
An integration is not built until it has read one.
One complete job of yours
Driven through the finished product, producing the real deliverable, before the engagement closes.
An honest list of what is absent
Delivered alongside what is present. What a system does not do is a buyer's right to know.
The vendor pack
A short list, so nobody has to go looking. Ask once and the whole set arrives together. If your procurement process has its own forms, send them and we will complete them rather than asking you to accept ours.
Mutual NDA
On request, before detail.
Entity and tax documentation
On request.
Certificates of insurance
On request, to your limits.
Master services agreement
On request.
Statement of work
Per engagement, in scope.
Security questionnaire
Completed by us.
References
Matched to your sector.
Escrow arrangement
Where your review requires it.
Capability statement
Two pages, on request.
Programs nationwide, United States. To start: call (252) 666-7217 or email [email protected].