← All projects
02 / Linked Helper / 2025–26

One app. Multiple accounts.

Taking a desktop product beyond a single account meant changing how the application requests, displays and exports data — and how the backend handles workspaces and billing.

Commercial · shipped
Cloud DB — product details & image source ↗
Linked Helper Cloud CRM with a Viewing as account selector and campaign filters
Cloud CRM — account selection and filters in a shared interface. Product image from the official Linked Helper Cloud DB page.
Linked Helper campaign profile picker with selected CRM leads and a multi-account filter
Campaign profile selection — choose an account, filter CRM profiles and add selected leads to a campaign. Product image from the official Linked Helper Cloud DB page.
RoleFullstack Developer
Company / productLinked Helper
StackReact · Electron · NestJS · TypeScript

The account boundary

I built and shipped multi-account support, reworking React architecture, contexts, API requests and exports. Users can view campaigns and messages across accounts in a single application instance. The product images above show the account selector in Cloud CRM and the campaign profile picker: concrete examples of bringing account context into shared screens and workflows.

Workspaces, end to end

I migrated account administration, access controls, billing and promo forms to workspaces, and moved the backend promo logic from organizations to workspaces using NestJS.

AI features with billing attached

I delivered the text-generation configuration UI, generation-service integration, and token calculation and charging. AI replies and outbound message generation shipped to production.

Making the codebase easier to change

I introduced Storybook, adapted Webpack and migrated to React 18 while resolving incompatible UI dependencies. Stories covered core components; Jest tests covered backend features and fixes.

← More workDiscuss this work ↗