Services

What you can hire me for

AI has made building things faster, but what comes after the build has not gotten any simpler. From rescuing a program that won't run to rebuilding an entire workflow, this is the work I do.

If your situation looks like one of these, read on

  • AI wrote it for me, but it won't run, and I can't tell what's wrong
  • Every time I ask AI to change something, something else breaks, and it keeps getting harder to undo
  • It works, but I don't dare ship it, and if something goes wrong, no one will clean it up
  • The person who built it has left, and no one now dares touch this code
  • I do the same repetitive tasks every day, know they should be automated, but don't know where to start
  • We bought the tools and opened the accounts, but the team still goes back to the old way of working
Core service

AI project rescue

Something built with Codex or Claude Code has gotten stuck, but rewriting it all would be a waste. You can also talk it through with me.

  • Emergency Rescue

    It won't run, it won't go live, and it keeps getting worse with each change.

    • Stop the bleeding first, so it runs and can go live
    • Find what is actually broken, instead of endlessly switching approaches
    • When the job is done, I tell you where risks remain
  • Codebase Takeover

    Organize it into a system you can keep changing with AI.

    • Organize the architecture and remove duplicated and roundabout code
    • Add tests, a deployment process, and documentation
    • After the handover, you keep changing it with AI, without needing to keep someone on staff just to maintain it

Same AI, but knowing where to look makes the difference

AI will do what you ask, but it won't tell you what to ask. When you are stuck, it is usually not that AI can't write the code. It is that you don't know which layer the problem is on.

  • The same error message could be a coding mistake, or a problem with the environment, permissions, or deployment. Work out which one it is first, so you don't keep fixing the wrong place
  • AI always gives you an answer that looks reasonable. To tell which one really solves the problem and which one just hides the symptom, you need to understand what it is doing underneath
  • Some problems cause no trouble now, but only after launch. Knowing which ones to fix first and which can wait saves more time than rewriting everything

I do system development and operations day to day and have seen many situations like this, so I can pinpoint problems faster. If you have been stuck for more than half a day with no progress, tell me what is going on.

Built right

From zero to one, or doing it right the second time

  • Website Development

    Built for people to read, and for AI to read, understand, and cite. Structured data, semantic content, and friendliness to AI crawlers. When it is finished, it is the site that gets recommended.

  • System Architecture Development

    Back office, data integration, permissions, and deployment. We plan an architecture that can handle growth, rather than building first and figuring it out later.

  • AI Application Development

    Agents, RAG, and automated workflows for customer service, order tracking, and data organization, connected to the tools you already use.

Actually used

After it is built, people really use it

  • Process Redesign

    Find out where the bottleneck is first, then decide whether a tool is needed. Often the problem is not the software but the process itself.

  • Corporate Training

    Customized workshops that get your team actually using AI in daily work, instead of taking the course and then letting it sit.

Process

How to get started

  1. 01

    Start with a conversation

    Describe where you are stuck in writing. Text back and forth is enough, with no need to hold a meeting first or have a finished plan.

  2. 02

    Review first, then decide

    I will look at your situation directly and tell you where it is stuck, whether it can be rescued, and whether it is worth doing. If I can't do it or it isn't worth doing, I will say so.

  3. 03

    Agree on scope and cost

    Once we agree on the direction, we talk about how far to go, how long it will take, and how much it costs. Nothing starts until the scope is agreed.

Projects vary a lot in size, so pricing is discussed only after I have looked at the situation. The website does not list a fixed price. If you want a rough idea of the range, just ask me and I will tell you.

Past work

What you can see directly

Most client projects cannot be made public, so what is shown here is what you can see directly. If you want to know what I have done in a particular category, ask me, and I will tell you within the limits of confidentiality.

FAQ

What you may want to know first

How are fees calculated?

We discuss pricing after I have looked at the situation, and the website does not list a fixed price. Projects vary a lot in size, so we need to talk before I know how far it goes. If you want a rough idea of the range, just ask me directly.

Do I need to prepare specifications or documents first?

No. Just describe where you are stuck. Text back and forth is enough, with no need to hold a meeting first or have a finished plan of what to build.

Will you take over code that AI wrote?

That is my core service. For projects that got stuck after being built with Codex or Claude Code, I can first bring them back to a working state, or organize them into a form you can keep changing with AI.

What if you look at it and decide it is not worth doing?

I will tell you directly. If I can't do it, or the cost does not match the result you would get, I will say so. I won't take the job just to take it.

Will I have to keep hiring you for maintenance?

No. After taking over a project, I add tests, a deployment process, and documentation. After the handover, you keep changing it with AI yourself, with no need to keep someone on staff just for maintenance.

What does corporate training include?

Customized workshops, designed around the work your team actually does, with the goal that people really use what they learn afterward, instead of listening and letting it sit. If you want to talk, tell me your team size and the problem you want to solve.

Talk to me directly

You don't need to decide what to build or prepare specifications first. Tell me where you are stuck, and we will look at how to solve it together.