Skip to content

A Biotensis service

The systems your operation quietly depends on, built to age well.

Long-horizon engineering for clinical software, regulated workflows, and the systems that earn their keep by being there in five years' time.

Talk to us → See consulting

The problem

Software that has to be there in five years is a different discipline.

A weekend prototype and a system that runs a clinic at 3 a.m. on a Sunday share almost no DNA. We do the second one, operationally durable, defensible against audit, recoverable when something fails, and shaped so the team that inherits it can actually keep going. The shortcut is not always faster.

What we build

  • Clinical & regulated software

    Workflow systems for hospitals, clinics, and labs, built to live inside the regulatory and operational realities of the institutions that run them.

  • AI-augmented workflows

    Machine learning and computer vision integrated into real production systems, with clinicians and operators in the loop, not demos that never ship.

  • Cloud-native platforms

    AWS, Azure, or hybrid deployments designed to scale economically and recover predictably. CI/CD that an on-call rotation can actually live with.

  • Integration & interoperability

    HL7, FHIR, REST, SQL, message buses, the connective tissue that makes sure your new system doesn't become another silo.

  • Long-term operations

    We stay through production, not just to launch. Most of our engagements are measured in years, not sprints.

  • Pragmatic modernization

    Strangling legacy systems on a schedule the business can absorb. We don't believe in big-bang rewrites.

Questions

What does a typical engagement cost?
Discovery + a foundational delivery is usually 3–6 months and a small senior team. We scope precisely after the discovery phase, with a fixed shape and a transparent budget.
Do you only work in healthcare?
No. Healthcare is our deepest experience, but the engineering practice (regulated data, long-lived systems, high-reliability operations) translates to finance, enterprise transformation, and any setting where reliability matters more than novelty.
Will you sign a fixed-price contract?
We prefer fixed-shape over fixed-price. We'll commit to a precise scope, team, and timeline, and we won't surprise you mid-engagement.
Do you work onsite?
Mostly remote, with onsite for discovery and at key milestones. Lisbon-based, EU time zones.
Can you take over an existing project?
Yes. We've inherited everything from green-field prototypes to two-decade legacy systems. The first phase is always an honest read of what you have.

How the engagement runs

  1. 01

    Discovery & shaping

    2–4 weeks. We sit with your team, map the problem, and write a shaped scope, not an estimate, a plan with sharp edges.

  2. 02

    Foundational delivery

    8–16 weeks for the first vertical slice in production. Real users, real data, real feedback before we've spent the budget.

  3. 03

    Steady state

    Ongoing engineering against a roadmap you control. Cadence, team size, and spend adjust to where the work is, not where the contract was signed.

  4. 04

    Handoff (when it makes sense)

    If you want the system in-house, we plan and execute the transition deliberately, documentation, pairing, and a clean handover, not a cliff.

How we work

Reliability is a feature
Uptime, recoverability, and observability sit on the same priority list as the next release. Not a separate one.
Boring tech, used well
Postgres, .NET, Python, TypeScript, Kubernetes where it earns its keep. We pick stacks your team can hire for in five years.
Small, senior teams
Two to five engineers, all senior. Less coordination tax, faster decisions, fewer meetings about meetings.
Open about cost and risk
If something is going to take longer or cost more than it should, you'll hear it from us before it shows up in a status report.

Have a system that needs to last a decade?

Start a conversation →