How to commission a custom build

Fit

What I take on

• Personal AI secretary

  Calendar, notes, and recurring tasks via chat and tools — personal or small-team.

• AX · work agents

  Team routines run by agents, with human checkpoints on critical steps.

• Backend · business systems

  Java · Spring · Kotlin APIs, auth, and domain rules built for production use.

Prep

What helps me reply faster

Nothing is required. Share what you have — I’ll propose a scope.

• One-line outcome (who should do what better)
• Must-have features (3–5) and nice-to-haves
• Tools/data to connect (calendar, Slack, internal APIs…)
• Rough timeline · budget band (undecided is fine)
• Links, existing demos, or screenshots

Process

After you send a request

Share a rough scope — I’ll propose a fit.

1. 01

   Share scope

   Goal, must-have features, rough timeline. Form or email both work.

2. 02

   Clarify & propose

   A short call or async notes to firm up scope, approach, and rough schedule.

3. 03

   Demo & quote

   I’ll show a related demo when useful, then align estimate and milestones.

4. 04

   Build & handoff

   Build to the agreed scope and hand over something you can actually run.

FAQ

Before you write

Core answers from the home FAQ.

What can I commission?

Personal AI secretaries, work/AX agents, and Spring·Kotlin business systems. Share the scope and I’ll propose a fit.

How does pricing work?

I estimate from features, timeline, and integrations, usually by milestone. Budget bands on the form are optional hints — exploring is fine.

What’s the difference between a demo and a delivery?

Demos are showcases you can try. Delivery is scoped to your data, permissions, and ops — built for real use.

Is remote work OK?

Yes. Most commissions run async with short calls. On-site only if we agree.