Skip to content

Embedded front-end team · United Kingdom

FE fundinfo:
a theme manager for branded fund documents, built inside the client's team.

FE fundinfo connects the investment industry through fund data and technology. Our front-end developers worked with its team on a Documents Admin and Theme Manager tool: the application its designers and business analysts use to build and manage branded financial documents.

FE fundinfo logo

Financial Services · Fund Data & Technology · www.fefundinfo.com

FE fundinfo's homepage: 'Navigate complexity with confidence' over a teal wave, under the Nexus by FE fundinfo menu
FE fundinfo's homepage · captured 20 October 2026The website is the client's own; our work was inside its application.
About the client

FE fundinfo
Financial Services · Fund Data & Technology

FE fundinfo is a fund data and technology company. In its own words, it connects the investment industry through trusted data and intelligent workflows, for investment managers, distributors and advisers.

Document production is part of that work. Ours sat inside it: a tool the client's own designers and business analysts use to build branded financial documents.

The challenge

What had to change

  • 01Requirements often arrived as scattered PDF specifications, leaving designers to fill the gaps.
  • 02Designers relied on manual tools to find template paths and track versions.
  • 03Themes could not be cloned and tailored for one client without rebuilding them.
  • 04Documents had to stay confidential across development, staging and live environments.
What we delivered

The solution

A structured brief

Solution

A predefined format for design inputs, agreed with the business analysts, so a template's specification reaches the designer intact.

A theme manager

Solution

Designers clone a theme and tailor it for one client, with modular CSS and JavaScript that extend templates without touching the shared markup.

Templates that can be found

Solution

Template tracking and version management connected to the existing cloud storage, in place of manual path extraction.

Secure document generation

Solution

Role-based access and PDF Reactor document generation across development, staging and live environments on Microsoft Azure.

Front-end capacity inside the team

Solution

User-interface development alongside the client's own team, wherever the project needed additional technical capacity.

Exhibit

How the tool is put together,
from brief to branded document.

Each stage of document production has its own layer, so a theme can change for one client without touching the others.

Exhibit · application architectureIllustrative
  1. Layer 1PeopleSees: Business analysts, designers, fund manager teams

    Analysts submit structured inputs, designers clone and tailor themes, fund teams view the branded documents.

  2. Layer 2Front endSees: Design-input forms, theme manager, template browser

    The screens our developers built with the client's team.

  3. Layer 3Theme layerSees: Modular CSS and JavaScript, role-based access

    Client-specific themes on shared component logic, with access governed by role.

  4. Layer 4Document generationSees: PDF Reactor

    The same rendering in development, staging and live.

  5. Layer 5Storage and trackingSees: Cloud storage and version tracking

    Templates found by version, documents stored securely on Microsoft Azure.

Redrawn from the architecture diagram in the delivery record; no client data.
The stack

Technology

  • HTML5
  • CSS3 and Sass
  • JavaScript
  • PDF Reactor
  • Microsoft Azure
Project outcomes

The results

A Documents Admin and Theme Manager tool in the client's own workflow

Themes cloned and tailored per client instead of rebuilt

Template versions tracked in one place

Role-based document generation across development, staging and live

Lessons

What other teams can take from this

Fix the brief before the build

A predefined input format saves more time than any tool built after it.

Clone, don't rebuild

When every client needs its own look, write the shared parts once and keep the differences small.

Environments are a security boundary

Keeping development, staging and live apart is what stops a draft document reaching the wrong reader.

Why they chose this team

Why PixelCrayons

  • Front-end developers who fit into the client's team and work in its tools.
  • Interface work for complex internal applications.
  • Capacity added where the client needs it, for as long as it needs it.

PixelCrayons provided frontend development support for our application and worked on the user interface with our team. Their developers were able to fit into the project and contribute where we needed additional technical capacity.

FE fundinfoFund data and technology · UK

The services behind this result

Front-end developers inside your team are a service you can buy on their own.

Want a result like this
on your own numbers?

A senior strategist records five minutes on your website: speed, search rankings, AI visibility, conversion leaks. Yours to keep, no strings.

No retainer required · NDA standard

Last updated