Operator first, consultant later.
Eight years of Mittelstand operations at Volt, Kryptonim, Testfast, Schippke und Partner. I had the problems myself before I solve them for you. Operator first, open-ended advisory in the Audit, no endless strategy roadmaps. Solo, by design.
What I built before.
These numbers are not consultant case studies. They are outcomes from roles where I was the operator. The method comes from that.
FinTech backbone for 80k active users. SEPA, compliance, treasury ops.
TPV throughput, MiCA compliance, EU license ops, regulator audits.
GDPR-compliant test operations network, RKI interface, realtime reporting.
SchippkeOS client platform, tax firm with 80 staff.
Eight years of Mittelstand and startup.
From the first code commit as a working student to solo implementation engineer. Every stop showed me where the Mittelstand actually gets stuck.
Janis Tirtey Consulting
Set up solo because most AI strategy vendors deliver PDFs and no one takes the implementation. Six-Step-Plan method, fixed price per phase, DPA on day one.
Schippke und Partner
Built SchippkeOS. Client platform with workflow automation, MCP bridges to DATEV, Office, Drive. First Claude-based workflows live.
Testfast
200+ test sites, GDPR-compliant backbone operations, RKI interface. Realtime reporting under regulation, scaling from 5 to 200 sites in 12 weeks.
Kryptonim
EU custody license, MiCA preparation, 6 million euro TPV daily. Treasury, reporting, compliance operations for regulator audits.
Volt Bank
FinTech backbone, SEPA integration, treasury ops. 80k active users, BaFin preparation, Series A scaling.
WHU + early startups
WHU Otto Beisheim School, parallel code commits in two pre-seed startups. First Mittelstand mandates as a working student for workflow automation.
Why I work solo.
Three principles that guide every engagement. If I build a team, they get lost, hence solo. At most two active engagements at a time.
Implementation as the main work
I deliver code, not PDFs. In the Audit I advise you open-ended, fixed price, with a recommendation on what is worth building. In the Pilot I build. If you want an endless AI roadmap, there are better addresses.
Fixed price, never day rate
Day rates create wrong incentives. With fixed price per phase we both share the risk that the phase delivers its output. Nobody benefits from delays.
Handover, never lock-in
A good engagement ends with no one having to call me anymore. Runbook, training, on-call rotation, code in your IT git. No consultant lock-in.
Kraków for operations, DACH for mandates.
Sole proprietorship in Poland, clients in DE and AT.
Polish sole proprietorship with EU data residency. Reverse-charge invoicing to DE B2B, tax residency Kraków, downtown office for deep work, travel to DACH for kickoffs and workshops.
EU, GDPR, CET
Why Kraków and what that means for your invoice.
Solo from Kraków is not a workaround. It is why the math works.
EU law, EU data, EU servers.
Poland is an EU member state. GDPR applies one-to-one. Your data protection officer ticks the country in two minutes.
Reverse-charge for German B2B customers.
You pay net, VAT is handled in Germany. Your tax advisor knows the procedure.
Lower payroll overhead = fixed price possible.
A German consultancy cannot build the same pilot for 14,000 EUR. Kraków is not a risk, it is the precondition.
Solo continuity plan
What happens if I get sick is the most common question.
Backup operator named. IT liability insurance 2M EUR. Full commitments formalised in the pilot promise.
Solo continuity plan on /pilot-promiseThree ways to reach me.
First contact goes directly to me, no sales team, no BDR. Reply within 24 hours, usually faster.