Why is there no price list on the page?+
Engagement names are stable; the price depends on your setup. Typical budget bands: Diagnostic from €1,500. Baseline from €6,000. Build typically €15,000–€45,000. Partnership from €3,500 per month. One email describing your setup gets you one real number instead of a menu that misprices the work.
How long does a typical engagement take?+
A diagnostic is one focused session. A baseline takes two weeks. A build is usually four to eight weeks of delivery time. Partnership engagements run monthly with a 90-day minimum. The shape is fixed before any work starts, so the timeline is a commitment, not an estimate.
Do you only work with one platform?+
No. Microsoft is a strong lane, but the work starts with the operational outcome. I also cover internal apps, portals, dashboards, workflow automation, implementation, and delivery.
Where do you work — Vienna only?+
Based in Vienna, with on-site working sessions in and around Vienna on request and online collaboration beyond that. Travel is handled explicitly in the scope rather than buried in it.
What happens if the work expands mid-project?+
The base scope stays fixed. If new work appears, we either park it for a later engagement or formalize a written extension. The boundary stays visible on both sides.
How do you handle data and GDPR?+
All client data stays in your tenant — Azure, Microsoft 365, Supabase, your own Postgres. I do not operate a parallel data store. Work runs inside your existing security and compliance perimeter; I do not require you to take on a new vendor processor. The site itself uses Plausible (privacy-friendly, cookieless) and no third-party trackers. Data residency, retention, and access controls are agreed in writing before the engagement starts.
Is the work accessible (WCAG)?+
Yes. Internal applications ship to WCAG 2.1 AA as the baseline, from day one, not as a follow-up sprint. Keyboard navigation, screen-reader semantics, focus states, colour contrast, and reduced-motion preferences are part of the build, not optional polish.
Who owns the code and the documentation?+
You do, from day one. Code is committed to your repository inside your tenant or organization. No license, no source-code escrow, no me-on-the-hook for someone else to fix things later. Admin notes, runbooks, and the role-permission inventory ship with the code, in the same repo.
What if you are not available — illness, holiday, leave?+
Single-person engagements have a bus factor of one; I treat that as the buyer’s risk, not a marketing problem. Every engagement ships with written admin notes, a runbook, and a named internal owner before launch. A competent in-house or contract engineer can pick up the system from those artifacts. That is a deliverable, not a hope.
What languages do you work in?+
English is the primary working language. German for Vienna meetings and documents on request. Albanian when it helps.