Skip to content
FLANERY

Built to fit the business you actually run.

I’m Jaden Flanery. I build custom software for people whose work doesn’t fit anything you can buy — a nonprofit’s application system, a hundred students matched to fifty mentors in one evening, federal filings turned into a queue somebody can actually work.

Ask for a callHalf an hour. No charge, no pitch.
The Topeka Leadership Academy program page, headed “Eight dinners. Eight pillars.” over a photograph of a speaker addressing an auditorium.
Topeka Leadership Academy — public site, applications, student portal
The Eagle U Mentor Match entry screen, asking a student for a first name, last initial and group leader.
Eagle U Mentor Match — 150 people, one evening

Three systems, all still running.

Three sectors, three different problems, one person who built all of them. Every screenshot below is the running system, not a mockup of one.

The Eagle U Mentor Match entry screen: a student enters a first name, last initial and group leader, with no account required.

Eagle U · 2026

A hundred students matched to fifty mentors in one evening

The lead queue: people and companies with the filing signal that surfaced them, a score, a contact-reachability indicator and a workflow status.

Opulence Planning Group · 2026

Turning public filings into a queue somebody can actually work

Three kinds of work.

Custom builds

The system a business needs when nothing you can buy quite fits. Applications, client portals, admin consoles, internal tools — built for one organization, which is yours.

You get: A deployed application, hosted and running, with an admin area your staff use without calling me.

Four to sixteen weeks, depending on scope

Consolidation

Work spread across tools that don’t talk to each other. I replace them with one system, or connect the ones worth keeping so they stop disagreeing about the same facts.

You get: One system your team logs into, and a written record of what each old tool was doing before it went away.

Six to twelve weeks

Data and migrations

Getting records out of wherever they live now and into something you can query, with a reconciliation that proves every row arrived. Also the pipelines that keep them current.

You get: Your history in a real database, a reconciliation you can check line by line, and the old source kept as a read-only archive.

Two to eight weeks

Any of these sound like your week?

Training someone new means teaching them nine different tools.
Onboarding
Two systems disagree and there is no way to tell which one is right.
Trust in your own numbers
You pay monthly for software that does a fifth of what you need.
Spend
The process only works because one person remembers how it goes.
Key-person risk

What I can build.

Every line below points at something already shipped and still running. If I can’t point at it, it isn’t on the list.

Web applications

Full systems, not pages. Accounts and permissions, admin consoles, records, file and video handling, transactional email.

A nonprofit’s application intake, student portal and staff admin

Internal tools

The software a business needs but nobody sells: review queues, dispatch boards, status trackers, the thing currently held together by one person and their memory.

A live matching tool that ran an evening for 150 people

Data pipelines

Pulling records from public sources and vendor APIs, resolving the same entity across them, and grading how confident the result is field by field.

Federal filings turned into a deduplicated, scored queue

Migrations

Moving records out of whatever they’re stuck in and into something you can actually query, with a reconciliation that proves every row arrived and nothing changed on the way.

A nonprofit whose applicant history lived in workbooks

Deployment and operations

Domains, DNS, email, hosting, backups — the boring half that decides whether a system is still working a year from now.

Every system listed here is deployed and in use

Build
TypeScript · Next.js · React · Python
Data
Postgres · Supabase · row-level security
Run
Vercel · Cloudflare · scheduled jobs
Verify
Playwright · Vitest · accessibility audits

And what I build for myself.

Nobody paid for these. They’re here because they’re the part of the range you can go and check yourself, without asking anyone’s permission first.

The Ascent home page with the altitude gauge dragged to Expert, showing compound interest explained in terms of continuous compounding and effective annual yield.

Ascent

An adaptive learning platform built around a single control: drag the altitude slider from “explain like I’m five” up to expert, and the same concept is retaught at that level.

After every answer it suggests the next question worth asking — the part a beginner cannot supply for themselves.

Next.js · TypeScript · Supabase

Open it (opens in a new tab)
The Life Platform briefing: a dated greeting, the next thing on the calendar raised into a card above the fold, then today's schedule, an open-task list and a directory of the app's modules.

Life Platform

A personal operations app that opens as a briefing rather than a menu — the next thing on the calendar, the checklist, and what actually matters, assembled before you ask.

Every feature is a self-contained module behind a config flag, so someone else can switch off the parts they don’t want.

Next.js · Supabase · PWA

Private — it runs my own calendar, notes and finances, so it is shown rather than opened.

The lead engine queue: a filterable table of businesses with a fit score, a pain score, a status and a plain-language reason for each row. Every business name shown is fabricated demo data.

Lead engine

An internal prospecting tool. It collects public records on local businesses, scores them against a model of who is actually worth a call, and hands back a queue where every row carries the reason it is there.

Nothing in it contacts anybody. It assembles and ranks; the call is a decision a person makes, and there’s deliberately no send button to make that easy.

Next.js · TypeScript · Postgres · Supabase

Private — it holds real records on real local businesses, so it is admin-gated and shown rather than opened. Every business name in the screenshot is fabricated and every number is masked.

How a project runs.

Four stages, and you can leave after any of them. The map at stage two is yours whether or not I build anything.

  1. Step 01

    A call

    Half an hour. You tell me what you’re running on now, I tell you whether I can help. Sometimes the answer is no, and that’s worth knowing early.

  2. Step 02

    A written map

    I write down every tool and process you depend on, and where each one costs you time. You keep that document either way.

  3. Step 03

    Building

    You see working software every week. Nothing gets built for a month behind a curtain and then unveiled.

  4. Step 04

    Live, and looked after

    I deploy it, host it, and keep it running. You’re not handed a folder of code and wished luck.

Jaden Flanery

I learned the business before I learned the code.

I’m Jaden Flanery. I study Personal Financial Planning at the University of Missouri, so I spent two years on how businesses actually run — cash flow, records, what has to be documented and why — before I wrote software for one.

Since then I’ve shipped systems for three organizations and built several more for myself. All of them are still running.

Most people who can build a system have never had to reconcile one. I ask about your books before I ask about your stack.

Flanery Solutions is mine. You work with me directly — there’s no account manager, and nobody to hand you off to.

More about me

Ask for a call.

Tell me how the work runs now and I’ll reply with times, usually the same day. Half an hour, no obligation either way — and sometimes the answer is that I’m the wrong person for it, which is worth knowing early. Worst case, you walk away with a written map of your own systems.

Whichever tools, paper or people the work currently depends on — and where it hurts. A couple of sentences is plenty.

I reply to everything, usually same day.