Skip to content
Part of ELO — Embedded Logic Operations · Engineering Team Lead ↗

Venture Build

Frontgo

Fintech platform team deployment in Norway. Formed and ran ELO's dedicated engineering team (1 backend, 2 fullstack) for Frontgo, driving engineering practices, hiring/HR, and weekly/monthly reviews with the client's project manager as Vipps and a core financing system shipped and handed over to the in-house team.

Role
Engineering Team Lead (via ELO)
Period
2 years · 2022 — 2024
Stack
Vipps Integration · Fintech Architecture · Backend Integration · Engineering Practices · and 3 more
Place
Sandnes, Norway (Remote)
  • Front Payment

    Hired and led the team that took Vipps payments and financing to production.

$ wsl --mount /dev/sda3 ↳ ✓ mounted at /mnt/wsl/sda3$ ext4 read 1.8 GiB ⏎ ➜ 71ms · 4.2× faster$ █

3Engineers hired and led (1 backend, 2 fullstack)

Frontpayment needed to rapidly scale its core financing system and integrate Norway's dominant payment network, Vipps, to establish product-market fit. Rather than hiring immediately in a high-cost market, they partnered with ELO to deploy a dedicated engineering pod that could act with high autonomy and velocity.

01 / 02

The Opportunity

Fauzul formed and ran the team: one lead backend engineer and two fullstack engineers.

He led its hiring and HR and kept delivery aligned with the roadmap set by Frontgo's own project manager on the Norway side, under strict NDA constraints.

02 / 02

Execution & Handover

Building a secure financing system requires rigorous alignment between the engineering pod and business stakeholders.

Fauzul ran the weekly and monthly reviews with the client's project manager, solved communication and requirement problems before they reached the codebase, and translated evolving company goals into concrete engineering work.

The team successfully integrated Vipps and built the foundational financing architecture. After two years of scaling and establishing product-market fit, the team handed over the entire codebase and infrastructure to Frontgo's incoming in-house engineering team.

  • Engineering Practices & Integration Guidance. Set the team's engineering standards and advised on the Vipps and financing integrations to keep delivery clean and maintainable.
  • Hiring & HR. Hired the three engineers and led people management for the team, building a tight team optimized for low-overhead velocity.
  • Weekly & Monthly Alignment. Ran the recurring sync and alignment cadence with the client's project manager, unblocking communication and requirement gaps.
  • Manager-to-Manager Communication. Served as the engineering-side liaison to the client's PM and executive team, ensuring tight product-engineering alignment.

Decisions and why

  1. Client-Owned Roadmap, ELO-Run Team

    WhyFrontgo's own project manager owned the roadmap while ELO formed and ran the engineering team, letting the client bypass recruitment bottlenecks and run a pre-aligned team at speed.

  2. Weekly & Monthly Sync Cadence

    WhyMaintained tight alignment on evolving compliance and product requirements, minimizing sprint drift and backlog debt.

Technical highlights

  • 01

    Formed and ran a dedicated 3-engineer remote team (1 backend, 2 fullstacks); led its hiring and HR.

  • 02

    Advised on Vipps API integration for seamless mobile checkout flows in Norway.

  • 03

    Guided engineering practices for backend modules behind a multi-tenant financing ledger system.

  • 04

    Ran weekly and monthly sync and alignment with the client project manager.

Impact

  • Helped deliver a core financing system and Vipps integration, achieving product-market fit.
  • Kept a structured, documented codebase that allowed a clean handover to the in-house team.
  • Established a repeatable playbook for running cross-border teams via ELO.
Outcomes

By the numbers.

Vipps
Payment integration
2 yrs
Engagement duration
Visit project

See it in the wild.

This case study covers how Frontgo was built — these links open what ships today: the live product, repo, demos, and supporting material.

↗ Next case study

Anygum

Anygum is a working marketplace-style platform where anyone can host their own API and builders can compose bespoke apps that pull services from multiple vendors. Identity runs through Cloudsight — custom auth on Auth0 — so provider and consumer context share single sign-on, RBAC and org controls, multi-instance of the same app for different teams, easy telemetry, and a single payment funnel for consumption. Ideation started as an internal auth problem for SaaS distribution; it was spun out as Anygum. Elobooks.net uses it. Distribution limited wider market reach; the product itself works.