How we work

Every project begins with architecture and design by our founder, a full-stack web developer with 25 years of professional web development experience and more than a decade specializing in Drupal. (LinkedIn Profile)

Once the architecture is established, the project is assigned to one of our two-person development teams. One developer is responsible for implementation, while the other independently reviews and verifies the work. Every page is checked after every significant change.

How We Build

For standard development work, we make extensive use of AI-assisted development with Claude and Codex. The AI agents work through our own cooperative project-management system: one agent implements the work, while another reviews it. Their output is then checked and verified by our development team.

Anything that falls outside established patterns — complex integrations, unusual functionality, architectural decisions or genuinely custom development — is handled directly by our developers and independently reviewed by the second team member.

This combination of experienced developers, AI-assisted development and continuous peer review allows us to build significantly faster than a conventional development agency, while typically operating at around one-third to one-quarter of conventional development costs.

Standards and Code Quality

We follow Drupal coding standards and established best practices throughout our work.

Our custom modules include automated tests, code is properly structured and documented, and we use Drupal's existing APIs, services and architectural patterns wherever possible rather than reinventing functionality unnecessarily. Custom controllers and other bespoke solutions are avoided where Drupal already provides a clean, maintainable solution.

The objective is not simply to make a website work. It is to produce code that another experienced Drupal developer can understand, maintain and extend.

Documentation and Continuity

Every project is documented at three levels:

• Code documentation — clear comments and documentation within the codebase.
• User documentation — practical documentation for the people who operate and manage the website.
• Technical documentation — architecture, custom functionality, important implementation decisions and information needed by future developers.

We deliberately design our projects so that customers are not locked into MADDev. If you decide to move to another developer or agency, they should be able to understand the system, take over the codebase and continue development without having to reverse-engineer our work.

Good documentation isn't an afterthought. It is part of the product.