Independent products, enterprise systems and client projects. A closer look at the problems, decisions and delivery.
Selected client engagements are anonymized to respect confidentiality.
No cases in this category.
Research workflow
CongressInsidersFilings
Strategy research
Independent Product
Investivoq
Public market signals turned into systematic investment research, strategies and alerts.
Live product
Independent ProductLive product
Investivoq
An independent research product built around public disclosures, systematic strategies and a subscription experience. Research only — not a brokerage and not personalized advice.
Problem
Alternative-data signals usually live in filings, vendor feeds and private notebooks. Readers need a place to inspect strategy families and unlock deeper history without opening a trading account.
My role
Owner of the live product: discovery, architecture, implementation and ongoing delivery across the public site, research catalog, access model and alerts.
What I built
Public site: landing, pricing, FAQ, methodology, legal, news and shareable historical cases.
Strategy catalog for published families, curated picks and watches.
Subscription checkout with pluggable payment providers.
Email and Telegram alerts, including preference and stop flows.
Admin surfaces for jobs, data sources, ingestion and editorial publishing.
Architecture & decisions
Modular monolith: Spring Boot, Angular, PostgreSQL, Flyway and JWT, plus a Python research engine started as a job process. Access is subscription-based. Payment providers are feature-flagged so checkout can change without rewriting the research domain.
An inventory system evolved into a commerce platform and the operations behind it.
Live product
Independent ProductLive product
Pets pets pets
A product that grew with the business: from inventory management to a connected online store and operational tools.
Originally built as Taxventory, an inventory management system, the platform evolved into Pets pets pets’ online store and operational backbone.
Problem
Catalog, channels and shop content drifted apart. Inventory work had to become a store that can search, sell, take payment and keep product data consistent.
My role
Co-founder and engineering lead: responsible for architecture, storefront and operator tools, checkout, payments, delivery integrations and the underlying inventory system.
What I built
Public storefront: home, search, category and product pages, cart, checkout, account orders and legal pages.
Operator console for orders, merchandising, delivery and tax configuration.
Inventory and reporting console retained from the original system.
Channel sync, payments, locker and courier checkout, and catalog feeds.
Architecture & decisions
One evolving monolith instead of a separate shop rewrite. Inventory routes remain; default routes are the store. Checkout validators define locker, courier, same-day local delivery and a national parcel option.
Architecture and technical leadership across multiple teams delivering digital healthcare.
Architecture & leadership
Enterprise EngagementArchitecture & leadership
Enterprise Telehealth Platform
Technical architecture and delivery leadership for a multi-team digital healthcare platform.
Problem
A multi-team telehealth estate needs one architectural direction, a coherent data model and release coordination across squads.
My role
Technical Architect / Tech Lead: high- and low-level design, database design, client-facing technical work, technical leadership of three teams and release coordination.
What I built
Architecture and design artifacts.
Database design.
Team technical direction and release coordination.
Architecture & decisions
Multi-team delivery under a shared high-level and low-level design, rather than isolated squads.
Technologies
Java
Spring Boot
Angular
PostgreSQL
AWS
Kubernetes
Outcome
Delivered as a live enterprise telehealth platform.
Case boundary
The client identity and internal implementation details are omitted.
Platform modernization
Legacy
Domain servicesData platformCloud delivery
Enterprise Engagement
Cloud Platform Modernization
Designing a phased transition from a legacy estate to cloud services and domain-oriented data.
Migration architecture
Enterprise EngagementMigration architecture
Cloud Platform Modernization
Architecture for a phased migration from a legacy application and database estate to a cloud platform.
Problem
A domain-heavy legacy stack cannot cut over in one step. Data and writes have to move without stopping the business.
My role
Architecture and modernization design: target-cloud and data model, domain boundaries, and the coexistence patterns needed to move writes safely.
What I built
Target-cloud and data design.
Domain boundaries and coexistence of legacy and new systems.
Shadow mode, transition bridge, outbox and dead-letter handling.
Architecture & decisions
Strangler-style coexistence rather than a single big-bang rewrite. Java, PostgreSQL and cloud delivery, with domain-oriented data boundaries.
Technologies
Java
PostgreSQL
AWS
Outcome
Migration architecture and integration patterns are defined.
Case boundary
Internal programme and client names are omitted. The case focuses on migration architecture.
Interactive product prototype
Grow in roleMove upSwitch track
Client Project
AI Talent Development Platform
From skill evidence to career options: product architecture and a guided employee journey.
Interactive prototype
Client ProjectInteractive prototype
AI Talent Development Platform
A product concept and interactive prototype for evidence-aware employee development.
Problem
HR and managers lack a shared, evidence-aware way to discuss skills and next roles. A slide deck does not let stakeholders click through consent, gaps and handoff.
My role
Business discovery with the client, product architecture, MVP scoping and a stakeholder prototype of the employee journey.
What I built
Product concept and logical architecture.
A three-stage delivery roadmap.
An interactive frontend prototype: sources → goals → competency profile → career paths → a demonstration development plan for a manager conversation.
Spec work for employee and role-model profiles, evidence labels, consent, skill gaps and manager handoff.
Architecture & decisions
An interactive frontend prototype using demonstration data, supported by a product concept, logical architecture and phased roadmap.
Technologies
HTML
CSS
JavaScript
Outcome
A clickable prototype for architecture and MVP conversations with stakeholders.
Case boundary
The client is anonymized. Demonstration data is not live employee information.
Operations & communication
FleetDrivers
Operations
Client Project
Fleet Operations Platform
A shared workspace for fleet records, driver search and operator outreach.
Live product
Client ProjectLive product
Fleet Operations Platform
An internal application bringing fleet information, driver records and outreach into one workspace.
Problem
Operations staff needed unit records, contacts and outreach in the same tool, with access limited by role.
My role
Requirements with the client through live delivery: discovery, architecture, implementation and launch of the working desk.
What I built
Workplace tabs for search, fleet records, management, statistics and outreach.
Domain model for units, drivers, equipment, owners, addresses and notification templates.
Role-gated management and messaging.
Scheduled outreach through a business telephony API.
Architecture & decisions
Internal monolith with signed-in roles for operations and HR. Messaging is invoked from a background task, not only from ad-hoc UI clicks.
Technologies
Spring
Angular
PostgreSQL
Outcome
The operations desk is live and in use.
Case boundary
The client, product name, domains and repositories are omitted.
Digital ecosystem
Central admin
POSWebsite / appChannels
Independent Product
Sushi Lovers
An interactive architecture proposal for one admin that publishes menu, price and content to every channel.
Architecture proposal
Independent ProductArchitecture proposal
Sushi Lovers
An interactive architecture proposal for a sushi restaurant group: why three admin panels cannot scale, and how one central admin should publish to every channel.
Problem
Point-of-sale, marketplace/QR admin and mobile-app admin hold overlapping menu and content. Each dish change is copied by hand.
My role
I wrote the architecture proposal: current-state analysis, target operating model, publishing design and a phased roadmap.
What I built
A bilingual interactive proposal covering analysis, target architecture, impact framing and roadmap.
PDF and standalone HTML export from the proposal page.
Architecture & decisions
Proposed, not implemented: a central admin as control plane; POS keeps kitchen, cashier and operational orders; marketplace/QR stays integration middleware; owned website and app consume the same published data.
Technologies
React
TypeScript
Vite
Outcome
A shareable architecture proposal. The restaurant platform itself was not built in this engagement.
Assessment protocol
Collaboration evidence
Assessment protocol
Capability profile
Independent Product
AI Passport
A capability passport for AI fluency based on observed collaboration, not token counts.
Prototype
Independent ProductPrototype
AI Passport
A capability passport for AI fluency: assessments of how a person works with AI, based on observed collaboration.
Problem
Most “AI skill” scores count activity. That measures usage, not effectiveness, and it rewards the wrong evidence.
My role
I designed the evaluation protocol and implemented ingest, a privacy guard, persistence and the private workspace.
What I built
A versioned evaluation protocol that refuses to score prompt, token or tool counts.
Ingest for protocol fetch and assessment submit.
A privacy guard that rejects raw emails, URLs, paths and code fences.
Persisted assessments and an authenticated workspace.
Architecture & decisions
A protocol-first backend: ingest and persist assessments, then aggregate them into a private capability view. Scoring is based on observed collaboration, not usage counts.
Technologies
Spring Boot
Angular
PostgreSQL
Flyway
Outcome
A working prototype of the protocol, ingest path and private workspace.
Generate and review
Business discovery
Digital audit
Site generation
Human review
Independent Product
Webvoq
Find local businesses, audit their digital presence, generate a site and wait for human review.
Prototype
Independent ProductPrototype
Webvoq
A pipeline that finds local businesses, audits their digital presence, generates a site and waits for human review before outreach.
Problem
Mass-generated sites look generic and go out without review. The useful loop is discover → audit → generate → review → deploy.
My role
I designed the pipeline and implemented campaigns, leads, digital-presence audit, site generation, human review and outreach.
What I built
Campaign and lead records.
Digital-presence audit.
Site generation, human review and outreach workflow.
Deploy and screenshot-audit hooks.
Architecture & decisions
Generation and hosting are adapter ports, not a single vendor hardcoded into the domain. Human review sits between generation and outreach.
Technologies
Spring Boot
Angular
PostgreSQL
Flyway
Playwright
Outcome
A working prototype of the discover → audit → generate → review loop.
Booking flow
Venues & trainers
Availability
Booking & payment
Client Project
Sports Booking & Management Platform
Search, profiles, reservations and operator tools for venues, trainers and group sessions.
Live product
Client ProjectLive product
Sports Booking & Management Platform
A multi-sided product for sports venues, trainers and group sessions: search, profiles, reservations, payments and operator tools.
Problem
Venues, trainers and sessions were not in one booking flow. Guests needed search and checkout; staff needed calendars and place management.
My role
Requirements with the client through live delivery: discovery, architecture, implementation and launch.
What I built
Public search for venues, trainers and workouts, plus place pages.
Booking and payment-complete flows.
Trainer schedule and venue-manager consoles.
Admin catalog, schedule, import and workflow settings.
Architecture & decisions
Role-separated surfaces for guests, trainers, venue managers and admins. Hosted checkout and webhook-confirmed payments.
Technologies
Spring
Angular
PostgreSQL
Flyway
Outcome
The booking platform is live and in use.
Case boundary
The client, product name, domains and repositories are omitted.
Trade-in flow
Device & condition
Vendor quote
Order & shipment
Client Project
Electronics Buyback Marketplace
Customers sell used electronics to approved vendors: catalog, quotes, checkout and shipment.
Live product
Client ProjectLive product
Electronics Buyback Marketplace
A buyback marketplace where customers sell used electronics to approved vendors.
Problem
Trade-in only works if device variants, condition grades, vendor quotes and return shipping share one order flow.
My role
Requirements with the client through live delivery: discovery, architecture, implementation of catalog, vendor quotes, checkout and shipment.
What I built
Public catalog, brand and type search, and product landings.
Vendor apply, dashboard and price-list management.
Customer cart and checkout with shipment and return addresses.
Vendor order lifecycle, including counter-offers.
Carrier integration for labels and tracking, with a port that can be disabled.
Architecture & decisions
Single API with separate customer, vendor and admin route trees. Shipment is a port, not a hardwired carrier.
Technologies
Spring Boot
Angular
PostgreSQL
Flyway
Outcome
The marketplace is live and in use.
Case boundary
The client, product name, domains and repositories are omitted.
Content delivery
Content
Platform
Delivery
Enterprise Engagement
Enterprise Learning Content Platform
Architecture and evolution of a learning-content platform: CMS, metadata, localization and delivery.
In development
Enterprise EngagementIn development
Enterprise Learning Content Platform
Architecture and evolution of a learning-content platform: CMS integrations, metadata, localization and delivery.
Problem
Enterprise learning content has to stay structured, localized and publishable across existing CMS and delivery channels.
My role
Architecture and platform evolution: CMS integrations, the metadata model, localization and content delivery.
What I built
CMS integration approach.
Metadata and localization model.
Delivery design for existing learning channels.
Architecture & decisions
Content stays structured in a shared metadata model, localized for each locale, and published through existing CMS and delivery integrations rather than a separate authoring stack.
Technologies
Spring
Angular
PostgreSQL
Flyway
AWS
Lambda
DynamoDB
Bedrock
Outcome
The first release was delivered to the staging environment.
Case boundary
The client and internal programme names are omitted.
Intake boundaries
Build vs buy
Boundaries
Proof of concept
Enterprise Engagement
Registration & Application Platform
Architecture and proof of concept for programme registration, membership applications and awards.
Prototype
Enterprise EngagementPrototype
Registration & Application Platform
Architecture and proof of concept for programme registration, membership applications and scholarships.
Problem
Programme intake, membership and awards sit across systems. The first job is to decide what to build, what to buy and where the boundaries are.
My role
Solution and vendor evaluation, build-versus-buy, system boundaries and a limited proof of concept.
What I built
Architecture and proof of concept for registration and application flows.
Integration outline across programme, membership and award systems.
Architecture & decisions
Evaluation-led: boundaries first, then a limited proof of concept.
Technologies
Spring
Angular
PostgreSQL
Flyway
AWS
Lambda
DynamoDB
Bedrock
Outcome
Proof of concept and architectural recommendation.
Case boundary
The client and internal programme names are omitted.
Education surfaces
Content
Classes
Marketplace
Enterprise Engagement
Digital Education Platform
Content, classes, conferences and a marketplace across several device types.
Live product
Enterprise EngagementLive product
Digital Education Platform
An education platform covering content, classes, conferences and a marketplace across several device types.
Problem
Content, live sessions and commerce had to work together on more than one client surface, including paid flows that meet card-industry controls.
My role
Architecture, database design, payment design under PCI DSS constraints, and load testing.
What I built
Platform architecture and data model.
Payment design under PCI DSS constraints.
Load-testing work for the education and marketplace surfaces.
Architecture & decisions
One platform spanning content, sessions, conferences and marketplace, rather than separate stacks per device.
Technologies
Spring
Angular
PostgreSQL
Flyway
AWS
Lambda
DynamoDB
Bedrock
Outcome
Delivered as a live education platform engagement.
Case boundary
The client and product names are omitted.
Content workflows
Documents
Workflows
Dashboards
Enterprise Engagement
Enterprise Document & Content Management
Customization of an enterprise document platform: dashboards, workflows and user functions.
Live product
Enterprise EngagementLive product
Enterprise Document & Content Management
Customization of an enterprise document and content platform: dashboards, workflows and user-facing functions.
Problem
A stock content platform does not match intake, approval and visibility rules without tailored dashboards and workflows.
My role
Requirements, functional design and development of the dashboards, workflows and user functions.
What I built
Custom dashboards, workflows and user functions on the document platform.
Architecture & decisions
Extend the existing content platform rather than replace it.
Technologies
Spring
Angular
PostgreSQL
Flyway
AWS
Lambda
DynamoDB
Bedrock
Outcome
Delivered the custom dashboards, workflows and user functions.
Case boundary
The client and platform product names are omitted.
Vision loop
Screen capture
Behavior library
Statistics
Enterprise Engagement
Computer Vision Poker Simulation
Real-time desktop recognition, a behavior library and statistics across 100,000+ hands.
Live product
Enterprise EngagementLive product
Computer Vision Poker Simulation
A computer-vision service that reads a desktop poker table in real time, applies a behavior library and records statistics across 100,000+ hands.
Problem
Table behavior and outcomes had to be observed from the screen and accumulated at scale for simulation and testing.
My role
Requirements, architecture and development of the recognition loop, behavior library and statistics.
What I built
Real-time computer-vision recognition of the desktop table.
A behavior library and statistics over 100,000+ hands.
Architecture & decisions
Classical computer vision and simulation. This is not a language-model or agent product.
Technologies
OpenCV
Outcome
Delivered a simulation and testing service covering 100,000+ hands.