Enquiries and product updates are separate
The contact form collects details so we can assess and respond to your request. Receiving updates about Jay requires a separate waitlist choice.
WORKING TOGETHER
Clear work. Clear responsibilities.
Good delivery begins with a shared understanding of the work, the information it needs and who takes responsibility. Here is how our website handles enquiries, what we agree for client projects and the principles shaping Jay.
Information you share on this website
A short description of your business need is enough to start. Keep passwords, access keys, customer records and confidential documents out of your first message.
Submissions stay in the site database
Form records are held in a local database on the server running this website and reviewed through an authorised admin interface. Those records are not sent to an AI service for analysis.
No advertising tracking
The site does not use advertising or visitor analytics cookies. Technical records may still be processed to serve pages and limit abuse.
The site guide is optional
When AI assistance is enabled, the question you submit is sent to Google Gemini to identify its topic. Earlier exchanges are not sent and the guide cannot retrieve form records or company documents. Keep personal, confidential and credential information out of your question. The privacy notice explains this separately.
What we establish for a project
We can own a new project from discovery and design through implementation and rollout. We agree deliverables, team responsibilities and decision ownership at the start, then keep track of them throughout delivery.
Scope and decision ownership
Agree the objective, deliverables, acceptance criteria and project plan. Track open decisions, dependencies and risks, and assess what new requests mean for scope and timing.
Data and access
Establish which information is needed, who may share it and which environments people can access. Address confidentiality, retention, deletion and any provider terms for the specific engagement.
Testing and rollout
Use operational scenarios to plan testing and acceptance, including data migration where needed, training and the cutover sequence. Establish approval and recovery responsibilities before rollout.
Handover and continued support
Specify the relevant source code, documentation, accounts and knowledge transfer. Make ownership of maintenance, further development and support explicit.
Jay: connections, data and decisions
Jay’s working development version uses application and data connections for analysis, reporting and workflows. General access is not open yet. This approach is not a security certification or a ready-made configuration for every organisation.
Connection and access scope
An application's API, data structure, access permissions and company policies determine the connection scope. Define which sources and operations each workflow can reach.
Sources and assumptions
Keep the records and assumptions behind a report visible. A difference between records is not presented as proof of an operational error or misconduct.
Human decisions at consequential steps
Define review and approval points for financial actions, policy changes and other consequential work. Monitoring regulations does not replace an authorised specialist's assessment of applicability.
Let’s establish the working arrangements.
If you need to clarify something before sharing information, mention it in your initial enquiry. We can agree what is needed and how to work together before going further.
Ask Jay