Senior engineer · Automation consultant

Senior technical help, without hiring a CTO.

  • Process automation for the work that eats your team's week.
  • AI adoption that reaches real work, not just a pilot.
  • A fractional CTO for the decisions you can't afford to get wrong.
20 years
building production software
~40%
of incoming x86 support calls resolved automatically, a team initiative at Sun and Oracle
150+
developers coached, so your team learns as we go

What I do

Three ways I can help.

  • This one

    Process automation

    Turn a manual process into software that runs.

    Orders retyped across systems, month-end reconciled by hand, the spreadsheet only one person understands. I map the process, decide what's worth automating, and build the smallest reliable system that fixes it.

    Talk it through →
    • Your team enters data once, not in five places
    • Plain, tested code for most steps, AI only where the input is fuzzy
    • Deployed, documented and yours to keep
  • This one

    AI adoption

    Get AI into real work, where it helps.

    You have licences, a pilot or a board asking about AI, but nobody has defined what it should do. We pick the workflows where it pays off, put validation and human sign-off around it, and teach your people to use it with judgment.

    Talk it through →
    • A clear view of where AI helps, and where plain code is better
    • One real workflow in production, not another demo
    • A team that can review and steer what AI produces
  • This one

    Fractional CTO

    Technical leadership, part-time.

    Someone to help decide what to build, which technologies to use, and how to get the most from your developers or agency. Hands-on, alongside your team, for a specific challenge or as an ongoing role. I spent 13 years in critical production environments at Sun and Oracle, have decided what to build and which technology to use as co-founder of Pybites since 2016, and have coached 150+ developers. You get that judgment, part-time.

    Talk it through →
    • Technology strategy and a roadmap tied to business priorities
    • Architecture, build-vs-buy and vendor decisions
    • Technical direction and review for your developers or external agency

How it works

It starts with a call.

Everything is custom, so there's no menu to pick from. Bring the problem, not a spec.

  1. 1

    A call

    We talk through what's costing you time or what you need to decide. If a spreadsheet or your current tools are enough, I'll tell you.

    Book a call →
  2. 2

    A written proposal

    Scope, timeline and a fixed price, shaped to your situation. If the problem needs mapping first, that becomes the first step.

  3. 3

    The work

    Your team builds it, we build it together, or I build it. Tests, monitoring and docs are part of the job, you own the code, and an optional retainer covers what comes next.

Proof

Not a demo. I run my own books on it.

Replacing my paid bookkeeping tool

The result: no more subscription. Closing the month is one step, my accountant can trace every figure back to its source, invoices can't be overwritten, and the data is mine.

The review step, narrated (in English).

Sun Microsystems & Oracle

13 years in critical production environments, around eight of them focused on support automation.

Pybites platforms

Python and Rust coding platforms I designed and built, in production for years.

Questions

Before you book

What happens on the call?

We talk through your situation: what costs your team time, or what you need to decide. No spec needed. Then I tell you what I see and what the next step would be.

What will it cost?

It depends on the work, so it's scoped after the call. You get a fixed price in writing before you commit to anything.

Do we need to use AI?

No. Most of a reliable business system is ordinary code, rules and tests. AI goes where it improves the outcome.

Who owns the code?

You do. All code and infrastructure built during the engagement belongs to your company.

Do we need our own developers?

No. If you have developers, I work with them and they keep the knowledge. If you don't, I build it for you.

Bob Belderbos

I'm Bob Belderbos.

I started in finance, automating reports at CHEP, then spent 13 years at Sun Microsystems and Oracle, around eight of them on support automation. So I understand the business process as well as the system behind it.

I've also coached 150+ developers through thousands of code reviews, which taught me to spot design problems early and to transfer ownership instead of creating dependency.

More about me →