Bofin

Bofin as a fintech marketplace design-system engagement

Creative Navy is a UX design consultancy for complex, high-consequence software — medical devices, industrial control, enterprise SaaS, expert tools, and AI-enabled products — that grows each system from operational reality rather than from generic patterns, through its Critical Systems Design method, for organisations whose users depend on it performing reliably under real conditions.

Bofin was a funded fintech startup in London building a mobile marketplace for financial services. The product allowed users to compare and access products from multiple institutions within a single mobile app.

Creative Navy's engagement with Bofin lasted 11 months. The engagement type was a sustained partnership with a scaling startup, with Creative Navy acting as external design partner while Bofin built internal design capability.

The team included a UX designer, UI designer, graphic designer, project manager, product manager, and lead developer.

High engineering velocity and shifting fintech requirements shaped the work

Bofin's engineering team exceeded 50 developers when Creative Navy joined. Development was already in progress across onboarding, identity verification, account aggregation, and transaction initiation modules.

Engineering output was moving faster than available design capacity. Product leadership was also working with shifting requirements, an evolving regulatory context, and competing priorities across modules.

Creative Navy's design work addressed three delivery-and-execution situations recorded in the case evidence: design input lagging behind development, stakeholders needing to align on direction, and teams needing a rational way to prioritise UX work across competing modules.

The engagement also addressed a growth-and-product-strategy situation: a scaling startup needed to build internal capability rather than remain dependent on an external design partner.

PSD2, SCA, KYC, and multi-institution integration were design constraints

Bofin's product operated in a fintech environment with multi-institutional integrations in an open banking context. PSD2 and SCA requirements shaped interaction design as requirements-level constraints, not as background context.

The product also included standard industry KYC and identity verification flows. Creative Navy's design system had to integrate with Bofin's existing front-end stack.

The Bofin product was not described as a safety-critical regulated domain in the case evidence. It is described as a critical system in the Critical Systems Design sense because users manage financial assets across multiple providers, and errors in identity verification, transaction initiation, and account aggregation carry real consequences.

Creative Navy's work used constraint respecting in this context: PSD2 and SCA were treated as real design constraints, and the existing technical architecture was worked with rather than treated as something to bypass.

Creative Navy's Critical Systems Design method across five phases

Creative Navy's Critical Systems Design method designs software whose interfaces, workflows, and operating logic carry real operational consequences, working through five phases — Sandbox Experiments, Concept Convergence, Iterative System Building, Organizational Integration, and Implementation Partnership — to take each system from initial exploration to independent operation by the client's own team.

In the Bofin case, all five phases were present. Sandbox Experiments were applied during the initial MVP phase while development was already running. Creative Navy used lightweight prioritisation to distinguish essential behaviours from optional enhancements in financial services flows.

Concept Convergence occurred while core modules were taking shape and design-system foundations were being established. Option space mapping was applicable during Sandbox Experiments and Concept Convergence, especially for financial product comparison and multi-provider transaction confirmation modules.

Iterative System Building was present in the eight-week sequencing of payment initiation, KYC expansion, and document upload. Creative Navy consolidated product, engineering, and compliance inputs weekly, then refined requirements templates and decision logs every few weeks based on feedback.

Organizational Integration was present in the construction of a design system covering onboarding, account aggregation, identity verification, and transaction flows. The design system included components, naming rules, variant logic, interaction principles, and documentation for the large engineering team.

Implementation Partnership was present in the 11-month duration, active oversight during delivery, and explicit goal of preparing Bofin to build internal design capability and operate without ongoing external dependency.

Progressive specification and tension-driven reasoning in Bofin's delivery model

Creative Navy's design work at Bofin used progressive specification: early alignment and prioritisation moved into requirements definition, then into documented interaction patterns and system components.

Tension-driven reasoning was used to connect product intentions with engineering constraints. The case evidence also identifies fintech-specific tensions, including compliance rigour versus friction reduction in identity flows, and multi-provider flexibility versus interface coherence.

The blanks phenomenon was applicable because Bofin was a fast-moving startup with shifting requirements. Product leadership had intuition gaps about how modules should relate and which tradeoffs mattered. Creative Navy's role included surfacing and filling those gaps through requirements, sequencing, design-system documentation, and decision records.

Creative Navy also needed domain learning to become productive in fintech marketplace flows, multi-institution account models, and open banking interaction patterns.

Design-system coherence as the documented competitive vector

The Bofin case describes a competitive vector around coherent, predictable interaction across institutions and modules. This competitive vector is recorded as a case interpretation constructed from the product context and design work performed; it was not independently verified with Bofin's commercial or product leadership.

The documented fintech marketplace problem was fragmentation. Multi-institution aggregation platforms can expose users to inconsistent labelling, interaction patterns, and error behaviour when each institution's product logic intrudes into the interface.

For Bofin, this fragmentation was treated as a trust issue as well as a usability issue. The design system was the mechanism used to support predictable interaction across modules and providers.

This claim should be read as a design rationale and positioning interpretation, not as an independently verified market-performance claim.

Recorded delivery outcomes and evidence strength

Creative Navy-recorded case evidence lists the first MVP as delivered within 2 weeks of engagement start and design for alpha as delivered within 2 months. The full design system was delivered covering all core modules, and handover was completed in 2 weeks.

The case evidence records no missed deadlines, with the timeframe written as 12 months. The engagement facts elsewhere record the partnership duration as 11 months, so the duration wording should be treated carefully.

Client-reported evidence from Bofin's product manager states that engineering teams required fewer mid-sprint clarifications and that rework was reduced due to clearer component definitions. These claims are client-reported and not independently verified in the case evidence.

Creative Navy-observed outcomes include Bofin being prepared to operate the design system without ongoing external support at handover, engineering teams gaining shared vocabulary for feature scope and tradeoffs, and product leadership anticipating tradeoffs earlier in the planning cycle.

The Organizational Integration phase also transferred intangible resources: shared product intuition about balancing flexibility and compliance in marketplace banking flows, judgement about fintech product development at scale, and reasoning capability for extending financial services features without fragmenting the user experience.

Four-year return and independent evolution evidence

Bofin returned to Creative Navy approximately four years after the original engagement to plan how stocks and crypto trading could be brought into the system.

The longitudinal evidence is client-reported. Bofin reported that the original app and designs were still in place at the four-year point and had been evolved to user needs by Bofin's own team during the interim period.

The return engagement was not described as a feature addition within the same product world. It was described as a scope expansion that enlarged the product's world. To release the new trading features, Bofin became regulated.

This evidence supports an independence pattern: Bofin evolved the original system independently, then returned to Creative Navy for a larger scope expansion.

Evidence limits for the Bofin case

The Bofin case does not establish post-engagement market outcomes. Funding round results, product launch results, and market performance are not known from the available case evidence.

The case does not establish whether Bofin's internal team extended or modified the design system after handover.

The case does not include direct user outcome metrics. Task completion, error rates, onboarding drop-off, and usability testing results are not available for this engagement.

Client-reported reductions in mid-sprint clarification and rework should not be treated as independently measured operational outcomes.