A considered connection.
From the outset.
We want to build useful software around established practice management systems. That starts with a conversation about fit, permission and responsibility.
Practice records
Reviewed documents and supported statement files
Dayanik workflows
Accounts · Payroll · Stock / Purchasing
Reception · Communications · Marketing
Official APIs
SOE EXACT · Dentally · Open Banking
Access and validation outstanding
Scope diagram, not a live network. Solid route: supported file-based workflows. Dashed boundary: prospective provider access. No automatic stock-to-ledger connection is implied.
| Proposed connection | Intended purpose | Current position |
|---|---|---|
| Software of Excellence SOE EXACT | Explore approved appointment context and reception workflows. | Prospective integration partner. No approved API access, current partnership or deployed connection claimed. |
| Dentally | Explore supported appointment and patient communication workflows. | Prospective integration partner. No approved API access, current partnership or deployed connection claimed. |
| Open Banking | Explore consent-based statement access for finance workflows. | Planned. Provider selection, commercial arrangements, access and validation outstanding. No active bank feed. |
| Manual statements | Import and review statement files within financial workflows. | Part of the product scope and locally developed Accounts work. This website does not import or process financial files. |
Product and company names are used for identification only. No endorsement is implied.
Fit first.
Access second.
Validation throughout.
Data scope, system ownership and permitted actions must be agreed before a production connection is considered.
Discuss the use case
Share module scope, intended users and the operational problem to solve.
Agree the boundaries
Confirm official access routes, permissions, data fields and permitted actions with the vendor.
Test in an agreed environment
Use an authorised sandbox or agreed test arrangement. Review failures, duplicate prevention and audit requirements.
Approve a controlled rollout
Complete technical, security, practice and commercial checks before live operation.
Start with the technical conversation.
Use-case scope, proposed architecture and approval boundaries are available here for review.
Show us the work
you want to make easier.
Choose your priorities. We’ll discuss the supported workflows, setup and the right next step for your team.