EN
Simon Miotk

Connect / Case study

Spoko Finanse systems

The website is the front door. The workflow is the work.

Role
Design · implementation · automation
Environment
Spoko Finanse
When / where
2026 · Poland
Spoko Finanse website, public-facing home page
Public website deliverable — not a screenshot of the internal CRM.
Context, decisions & execution

01 / Context

Context

A mortgage and insurance advisory needs both a clear public presence and a reliable route from enquiry to consultation.

02 / Problem

Problem

A website, a booking tool and a CRM can each work while the handoff between them still relies on someone copying information. That handoff was part of the implementation scope.

03 / Approach

Approach

Treat the public interface and the process behind it as one delivery scope. Design the enquiry path together with the booking and operational handoff.

04 / Personal ownership

Personal ownership

Concept, design, the Polish and English site, calculators, consultation booking connected to the CRM, domain and email configuration, and quality assurance.

05 / Execution

Execution

The site became a reusable foundation for later studio work. Related office automation includes refinancing analysis across advisers’ mortgage portfolios and mass client email workflows. The exact internal workflow and client data are not published here.

06 / Evidence and result

Evidence and result

The public site is available to inspect. Booking-to-CRM and advisory automation are documented scope; a quantified conversion, revenue or time-savings result has not been supplied.

07 / Next

Next

Add an anonymised walkthrough of one enquiry moving through the system, plus a measured before-and-after result.

Evidence

Inspect the record.

Asset pending

[ANONYMISED BOOKING → CRM WORKFLOW — RECORDING TO ADD]