https://handbook.unicis.tech/ 2026-05-25T08:49:35+00:00 https://handbook.unicis.tech/ https://handbook.unicis.tech/_media/wiki/logo.png text/html 2026-05-25T05:56:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/customer_onboarding?rev=1779688593&do=diff Customer Onboarding ← Back to Core Processes ---------- Purpose To take a new trial signup from first contact to an active, value-realising customer — consistently, within 14 days of signup. Owner Predrag Tasevski — CEO / Visionary Trigger This process starts when a new trial signup is confirmed — either via the unicis.tech signup form (Mautic notification) or via a direct outreach that results in a trial account being created. text/html 2026-05-25T06:10:43+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/eu_project_delivery?rev=1779689443&do=diff EU Project Delivery ← Back to Core Processes ---------- Purpose To deliver EU-funded project obligations (deliverables, milestones, reporting) on time, with clear internal ownership, and without disrupting core platform work. Owner Predrag Tasevski — Stakeholder & EU Projects Management text/html 2026-05-25T05:56:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/invoicing_billing?rev=1779688593&do=diff Invoicing & Billing " 🔄 Status: Draft — Will be updated when billing.unicis.tech is live." ← Back to Core Processes ---------- Purpose To issue invoices accurately, collect payment reliably, and maintain clean financial records — for customers, partners, and EU project claims. text/html 2026-05-25T05:56:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/partner_onboarding?rev=1779688593&do=diff Partner Onboarding " 🔄 Status: Draft — This process is defined but not yet fully operational. billing.unicis.tech and the partner programme are in development. Update this page when the partner programme launches." ← Back to Core Processes ---------- Purpose To onboard new reseller, integration, or referral partners into the Unicis partner programme — from first contact to active, contracted, and billing-enabled partner. text/html 2026-05-25T06:08:16+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/platform_release?rev=1779689296&do=diff Platform Release ← Back to Core Processes ---------- Purpose To ship Unicis Platform releases consistently, with clear quality gates, predictable communication, and no surprises for customers or the community. Owner Peter Zlatev — CTO Trigger This process starts when the team agrees a set of features/fixes is ready to ship — either at the end of a planned sprint or when a critical fix requires an unplanned release. text/html 2026-05-25T05:56:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/process_template?rev=1779688593&do=diff Process Template Copy this page when creating a new Core Process. Replace all placeholder text in [brackets]. ← Back to Core Processes ---------- [Process Name] Purpose [Why does this process exist? What problem does it solve? One or two sentences.] Owner [Full name] text/html 2026-05-25T05:56:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/start?rev=1779688593&do=diff Core Processes This section documents the Core Processes that run Unicis. A Core Process is a named, repeatable workflow that produces a consistent result. Every process has a single owner, a clear set of steps, and a list of the tools involved. Documenting processes is not bureaucracy — it is how Unicis delivers consistent quality as the team grows, onboards new Unicians, and operates across time zones. text/html 2026-05-25T06:13:52+00:00 Anonymous (anonymous@undisclosed.example.com) https://handbook.unicis.tech/pub/processes/support_resolution?rev=1779689632&do=diff Support Resolution " 🔄 Status: Draft — Review and approve at next Quarterly Session." ← Back to Core Processes ---------- Purpose To resolve customer and community support requests consistently, with clear response time expectations and a closed feedback loop. Owner