Leading a custom Adobe Commerce build for fundraising

Challenge

MarketNation runs a fundraising and donations business on Adobe Commerce. The domain does not fit a standard retail catalog. Campaigns and donations push the platform well past its default behavior. A small engineering team needed one person to turn business goals into an architecture and a plan of work they could ship without rework.

Approach

I lead a team of three engineers and own the path from idea to merged code. For each new requirement I check which parts of Adobe Commerce already cover the business need and where a custom module is needed. From there I break the work into tasks small enough to review in one sitting. I keep the roadmap and sequence the tasks so each release stands on its own.

On the technical side I set the architecture for the customizations, so they build on the platform’s own extension points. I review code against agreed standards and watch performance as the custom logic grows. The problems that sit deep in the platform land on my desk. I have worked on Magento and Adobe Commerce since 2009.

Result

The build moves forward in small releases instead of large, risky drops. The team works from one roadmap and a shared definition of done, and the review standards keep the codebase consistent as it grows. Because the custom features follow the platform’s conventions, they stay maintainable as requirements change. The engagement continues with the same team.