Athens · since 2024 · enterprise AI integrations
An integrator for
systems already
in production.
Praxis Ab Machina builds AI systems that run inside your infrastructure. Based in Athens, since 2024, in production across four sectors.
01 · Position
We are not consultants who advise on AI. We are the people who listen to your problem, design, build and support its solution.
The work is AI integration and custom AI solutions — taking an organization through AI adoption at whatever scale it is working at, from one painful workflow to a program across an estate. The method does not change with the size of the buyer, and neither does the standard.
We do not sell stacks. We sell outcomes, and we are fluent enough across many technologies, many model APIs, vector stores and most CRM, ERP and communications surfaces that the tool is a consequence of the problem rather than the other way round.
02 · Method
Six steps, one handover.
The same six steps run whether the engagement is one workflow or an AI platform. Small projects are usually live within three to five weeks of kickoff; larger projects run six to twelve.
- 01 Discussion session We sit with your team and shadow the work. The goal is not to impress — it is to find the one point where delays occur and problems are spawned.
- 02 Process cartography We map the existing workflow as it actually happens, not how it is drawn on the org chart. Bottlenecks, exceptions, and tribal knowledge get flagged.
- 03 System design A specification document — what the machine does, what it does not, where it asks for human intervention, and how we will know if it misbehaves.
- 04 Build & harden Iterative implementation in your stack, with logging, fallbacks, and human-in-the-loop checkpoints by default. We ship to staging before production.
- 05 Calibration window Two to four weeks of co-piloting alongside your team. Edge cases get ironed out, prompts get tuned, dashboards get sharpened.
- 06 Put into Production The system goes into production. We stay on retainer for evolution, monitoring, and the occasional surgical patch.
03 · Terms
Fixed fee or retainer. No hourly billing, and no surprises at the end.
- Pricing is per project, agreed before work begins.
- Most engagements open with a discovery sprint of one to two weeks, agreed in writing before it starts.
- The specification the sprint produces is yours.
- After it, either a scoped fixed price for the build, or a monthly retainer for ongoing evolution. Estate-scale discovery is scoped separately, before it begins.
04 · Governance
We work inside your security envelope, and we document it for your CISO.
- EU-resident infrastructure by default, and signed data processing agreements.
- Zero-retention model endpoints wherever the use case allows it.
- VPN, SSO and on-premise inference where your estate requires them. We adapt to the envelope rather than asking for an exception to it.
- Logging, fallbacks and human-in-the-loop checkpoints are defaults in every build, not options. Staging before production, always.
05 · The people
Ten people. The ones who design it, build and support it.
The people who scope your system are the people who build it, and the same people are on the call in week one and in month twelve. That holds at any size of engagement — a single workflow and an estate-wide program get the same method and the same governance.
- Ioannis KarygiannisFounder · Principal Engineer
- Nikos D.Integrations Lead
- Athanasios A.Principal Project Manager
- Giannis A.Communications Manager
- Tryfonas P.Senior Integrations Engineer
- Marios K.Principal UI/UX Designer
- George K.Principal Systems Engineer
- Konstantinos D.Senior Systems Engineer
- Kyriakos X.Senior Systems Engineer
- Korina A.Principal AI Adoption Strategist
06 · What we decline
We turn down work, and it is worth knowing which.
- Your Headcount replacement. We do not sell it and we will not scope it. The target is the busywork consuming your team’s afternoons, so the senior people you already pay for can do the work you hired them to do.
- Work we are not the right firm for. If the answer is a piece of software you can buy, or a process change with no system in it, we will say so — that conversation is cheaper for both of us than the alternative.
- Anything that has to make a decision about a person on its own. Every build we ship escalates those to a human by design, and that boundary is written into the specification before anything is built.
- Work we cannot staff without lowering the standard. There is no lighter version of the method above, and we would rather decline than run one.
07 · Next