Pricing is based on the complexity of the work. I start with my base day rate (for an 8-hour day) and estimate the total effort required for each milestone. From this, I calculate a fixed price that reflects the scope and technical requirements.

For example, if a milestone is estimated to take 12 hours, I internally convert the day rate to an hourly rate to calculate a fair fixed price.

The offer you receive is always a transparent fixed price, no hourly billing. This price includes all necessary work, including session time, research, planning, and a buffer for unforeseen challenges.

Milestones are clearly defined deliverables or outcomes as part of a project. A “project” can be anything - for example, a custom AI system, a gameplay feature, or a technical tool. This “project” will then be split into multiple milestones, each representing a concrete step toward completion.

I take full responsibility for each milestone’s implementation, including planning, coding, and testing, so you don’t need to provide technical direction – the work is fully handled on my end.

Each milestone has a fixed scope and a fixed price. While a milestone is typically equivalent to roughly one focused development day (8 hours), it is not billed as a daily rate and not tied to a calendar schedule. This is backed by the contract as a work contract (“Werkvertrag”) by law, meaning the agreement is for a specific deliverable rather than time worked. Milestones are scheduled flexibly based on scope, availability, and project needs. Workshops operate the same way, with the schedule being flexible and not tied to consecutive days.

Once a milestone is agreed upon, the price stays the same – even if it ends up taking more time or effort than expected on my end.

For more information, see the Terms & Conditions for full contractual details.

It’s important to come prepared – but don’t worry, you don’t need a finished design document or a polished project plan. At minimum, it helps if you have a rough outline or notes about what you want to achieve. Think of it like homework: a starting point for our discussion.

Bring energy and an open mind, because I’m going to ask a lot of questions – and I mean a lot, down to the tiniest details. This ensures we’re on the same page and we know exactly what we want to create. The more prepared you are, the smoother the workshop will go and the more accurate the resulting project plan and pricing will be.

Remember: everything we discuss in the workshop directly impacts how I execute your project and how much it will cost. Taking a bit of time beforehand to think things through will save us both time and make the final outcome much stronger.

The main reason is long-term reliability and support. I don’t own or control third-party tools, so I can’t guarantee they’ll stay compatible or supported throughout your project – especially by the time you launch your server. By minimizing their use, I help reduce technical debt and avoid future headaches. It also means I can fully stand behind everything I build.

For more detailed information on liability and third-party dependencies, you can review my Terms & Conditions.

A Binary Module is basically a more powerful type of addon for Garry’s Mod, written in C++ instead of Lua. Lua is the standard scripting language, but it has limitations. With a Binary Module, I can build things at the same level as the game's developers, directly interfacing with the engine to add or change functionality in ways Lua simply can't.

This allows for more advanced, optimized features and better performance. It’s more complex to develop, but it can be the best solution depending on what your project needs.

Because I have years of experience with this kind of low-level modding thanks to my background with SourceMod, I know how to implement it efficiently and in a way that lasts.

Yes. Sometimes I implement technical tools or features via mods, but if the developers added them to the official game, they could be used directly instead of through my workaround. In such cases, I can submit a GitHub pull request so the developers maintain it long-term, reducing technical debt on my side while also benefiting the modding community.

Yes. I offer standalone consultation sessions for technical guidance, planning, code architecture, or answering specific development questions. A consultation session is billed at a fixed rate of €590 for an 8-hour day.

I process payments securely through Stripe and currently support:

• Credit & debit cards

• PayPal (EEA countries only)

• Digital wallets (Apple Pay, Google Pay, MobilePay)

• Klarna (available in most EEA countries)

• Alipay

• Link

• iDEAL

• Bancontact

• EPS

• TWINT

I’m happy to be flexible if my prices don’t align with your cash flow or budget. We can split milestone payments into two (however, a 3% fee applies per milestone), or use PayPal or Klarnathrough Stripe (provided you’re located in an EEA country), which lets you pay in installments or at a later time. This way, a few options are available.

Milestones can also be spaced out to better suit the pace of your cash flow.