Custom Work

For the occasional problem that needs its own shape.

Most of the work here is public, free, and built because it seems useful. Once in a while, a private workflow or odd little business problem is interesting enough to build around.

Try the builds Ask on X

The Fit

The public work stays the center.

The free apps are not bait. They are the main thing I want people to use, share, remix mentally, and point at when they are trying to understand what practical AI can do.

Custom work lives off to the side: a small number of projects where the shape is specific, the problem is real, and the useful version would not exist as a generic app.

Use the builds Ask on X About Aaron

What Can Fit

Small tools for real edges.

The best custom projects are narrow enough to ship and specific enough to matter: private data, repeated decisions, awkward handoffs, or a workflow that keeps asking for a better handle.

Private Workflows

Give repeated work a tool that fits the room.

Some problems are too specific for a public app and too small for a traditional software project. Those are usually the interesting ones.

What this looks like

  • Private versions of public tools with your own inputs and outputs.
  • Small internal apps for repeated tasks, reviews, forms, or decisions.
  • Cleaner interfaces around messy AI prompts, files, or handoffs.
  • Practical scoping so the first version ships instead of sprawling.

Best for

People with a concrete workflow, a real constraint, and a useful first version in mind.

Common wins

  • A tool your team can understand without a training marathon.
  • Less copy-paste work between documents, chats, files, and spreadsheets.
  • Faster testing of a product idea before it becomes expensive.
  • A clearer answer about whether AI is actually worth using here.

Workflow Automation

When the problem is not an app idea. It is the work itself.

A lot of useful AI work is quieter than a product launch: summarizing, sorting, drafting, checking, routing, tracking, comparing, and turning scattered inputs into something a human can act on.

What I can build

  • Reporting and documentation helpers.
  • Prompted workflows for customer messages, content, or internal notes.
  • Dashboards that turn scattered information into something easier to manage.
  • Local-first tools where privacy, control, or offline access matters.

Best for

Businesses, creators, and operators who know where the work hurts but do not need a giant software project.

Why this approach works

  • Hands-on implementation instead of abstract advice.
  • Custom fit to your operations, not a generic software pitch.
  • Usually faster and more affordable than traditional development paths.
  • Built around your actual staff, constraints, paperwork, and customers.

How We Work Together

A simple path from rough idea to useful shape.

Start with the actual problem

Bring the workflow, idea, bottleneck, or awkward recurring task as plainly as you can.

Find the smallest useful thing

We look for the first version that would actually change the work, not the biggest possible system.

Shape the first useful version

We decide what the smallest worthwhile tool needs to do, what it should ignore, and how success looks.

Build only if useful

If there is a fit, I build toward a practical result instead of stretching the conversation into theater.

For Now

Start on X. Tip the free tools if they help.

The free builds are open first because they give people something useful before they spend money. If a tool helps, tips through X Money at @dicemanorama or CashApp at $dicemanorama help fund the next one.

For custom work, X is still the easiest front door. Public replies are great when the answer can help others. DMs are better when the context is private, weird, or too long for a thread.

Live booking is paused while the build-first offer takes shape.
Ask on X Tip with CashApp