Business systems & automation

Custom Software & SaaS Development

I build software around the way a business needs to operate. The starting point is a useful workflow and a clear data model, then the screens, permissions and integrations that support it.

Start a Project

Where the friction appears

What I can build for this scope

How I choose the technical approach

I choose the interface, API and storage around the data and operating constraints. Documented work includes React, TypeScript, FastAPI, MongoDB and Cloudflare Workers. Subscription features are available for scoping; the portfolio does not establish production subscription operations for every prototype.

How I deliver the work

I define roles and acceptance criteria, model the main records, build a usable workflow, then verify permissions, data transitions and integration failures. Handover includes the agreed deployment instructions and operating documentation.

Relevant work and its actual stage

ScoutFlow documents an 11-stage football transfer CRM prototype. OryolMail is a mail workspace in development; BelaPath remains a prototype. These projects demonstrate product structure and implementation direction with their actual stages visible.

ScoutFlow

Prototype

A football transfer and scouting CRM designed to manage players through a structured transfer pipeline.

OryolMail

Building

A personalized mail service for brands, combining domain-based inboxes, shared workspace operations and AI-assisted email workflows.

BelaPath

Prototype

An Africa-first platform for discovering, verifying and pursuing legitimate study, work and relocation pathways to Belarus.

Practical questions

Can you connect software I already use?

I assess available APIs, permissions, data quality and limits before committing to an integration. The result may be a direct connection, an import/export workflow or a smaller first step.

How do you keep the first version focused?

I identify one useful end-to-end workflow and its acceptance criteria. Secondary roles, reports and automation stay in a visible backlog until the core behavior is verified.

What testing and documentation are included?

I agree checks with the scope: key user journeys, data transitions, failure handling and relevant accessibility or device behavior. Handover documentation covers the agreed setup and operating needs; maintenance is scoped separately.

Start a Project

Tell me what needs to work.

Share the problem, existing systems and the outcome you need. I will use the details to assess fit and scope.

The enquiry service is not configured yet. You can contact me on LinkedIn. LinkedIn

Find your way.