A boutique firm for software that has to last.
Condactis is a small engineering consultancy specializing in enterprise architecture, integration, and custom platform development.
A small consultancy on consequential systems.
Condactis is a small engineering consultancy. We work with mid-market and enterprise clients on the parts of their software estate that are operationally consequential: ERP migrations, integration backbones, BPMS implementations, and custom platforms in regulated industries.
The work selection is deliberate. The systems we build are expected to operate for a decade. Most engagements involve regulatory constraints (GDPR, HIPAA), high uptime requirements, or integration with legacy estates where errors propagate expensively.
Two of our products, Clinidesk (orthopedic clinical workflows) and School Data Manager (educational data integration), are operated and maintained by the firm. Running production systems sharpens how we approach client engagements. Architecture decisions look different when the on-call rotation is your own.
How an engagement actually runs.
Engagements begin with architecture rather than code. Business process modeling, event flow analysis, integration boundaries, and compliance constraints are mapped before implementation begins. This phase is short, typically one to four weeks, but it determines the quality of everything that follows.
Implementation combines senior engineering judgment with AI-augmented code generation. Generative tooling handles boilerplate, scaffolding, and routine module generation. Senior engineers handle architecture, security boundaries, and the parts of the system where decisions matter. Every release is reviewed by an engineer with at least ten years of production experience. There are no unsupervised code paths in delivery.
The combination produces faster delivery than traditional consultancy timelines without the failure modes typical of unsupervised generation. The firm has operated this way for two years across both client engagements and proprietary products.
The firm operates on three principles.
Predictability
We choose technology that will still be operable in year five and year ten. Frameworks, runtimes, and vendors whose long-term support is uncertain are out, even when they offer short-term productivity. The choice of stack is a ten-year decision and is treated as one.
Systems thinking
The cause of a production issue is rarely where the symptom appears. We trace effects back to architectural causes, even when the immediate fix would be faster. The hour spent on root cause typically saves the next quarter of incident response.
Transparency
Clients have access to architecture decisions, repositories, and roadmaps from day one. When something goes wrong, communication is same-hour, not same-week. This is not a stated value; it is the only operating model that scales for systems of this complexity.
Engagement begins with a conversation.
Every project starts with a 30-minute technical discovery. The conversation is led by a senior architect and is intended to establish whether the engagement is a fit for both parties.
