terminal root@mbit:~# about --brief

M-BIT - solo practice, production-grade software

Since 2014, one developer-owner behind the name: WHMCS addons, custom web and desktop work, and WordPress / WooCommerce when you need more than a template.

The name and the person

M-BIT is what you see on email, invoices, and module licences. Legally it is a Croatian sole proprietorship (obrt) in Zagreb. You hire clarity, not a theatre of roles: the same person who estimates the work is the one who ships it and answers when something breaks in production.

Since
2014
Based
Zagreb, HR
Structure
Solo
Focus
WHMCS · Custom
receipt_long Legal & invoicing

M-BIT development - Zagreb, Croatia

Ulica 1. Gardijske brigade Tigrovi 25 10000 Zagreb Croatia

OIB
33812893661
IBAN
HR8123600001102578609
Bank
Zagrebačka banka d.d.
SWIFT / BIC
ZABAHR2X
forum Direct line

Same channels as the rest of the site - you always reach the person who does the work.

Get in touch

Working with M-BIT

How engagements run

Projects are scoped in everyday language first - outcomes, risks, and constraints - then refined with technical detail where it actually affects a decision.

  • WHMCS modules, bespoke web and desktop apps, WordPress / WooCommerce extensions - no invented delivery pods
  • Small jobs and rescue work are quoted as such; larger builds are split into milestones so progress and cost stay visible
  • Tooling follows maintainability - reliable, supportable defaults unless there is a concrete reason to diverge

Why people stay

Long-term clients tend to care about predictable production behaviour. That standard applies whether the piece is a commercial addon, a client portal, or wiring payments and CRM together.

  • Changelogs published for every release - you know exactly what changed and when
  • Documented assumptions and constraints left in code comments and handover notes, not just in someone's head
  • Support boundaries discussed upfront so there are no surprises when something needs fixing after launch

Ready to talk scope?

If you want to sound out a problem before locking scope, a short description of your environment and timeline is enough to start.