OSYRADiscuss a workflow

Contact / founder enquiries

Can we model
one of yours?

Start with one consequential action, the condition that may change before it is carried out and the outcome you want to improve. Workforce, purchasing and automated workflows are useful examples. No technical specification or live data is needed for the first conversation.

John Haigh / Founder

One clear problem
is enough to start.

If you own the work, tell us where the authority or operating conditions change. Platform, delivery and technical partners can describe an integration requirement. Investment and institutional partners can use the separate strategic enquiry below.

Email John

john@osyra.si

John Haigh on LinkedIn

Start from your perspective

Enterprise workflowOperational burden and current requirementsGovernment applicationPublic-service work and accountabilitySovereign deploymentInstitutional control, dependencies and exitPartner delivery or embeddingCustomer value and repeat implementationTechnical reviewA bounded question and relevant evidenceInvestment & strategic partnershipsFunding, distribution, engineering or institutional collaboration

Explore the fit.
Then agree the scope.

A first conversation can lead to problem discovery, selected evidence review or a scoped non-production evaluation. It does not require a purchase or production connection.

Keep the opening note non-confidential. Do not send personal, health, workforce or client records, credentials, security-sensitive information or confidential implementation details.

Email is not a confidential submission channel unless separate written terms already apply. An enquiry grants no licence, technical access or production-use rights.

Privacy and site notice