What we are good at building

WordPress, Shopify and Magento for commerce, Laravel and PHP for server side work, React and Node for interfaces and services, and AWS, Azure or Google Cloud for hosting. The expertise page gives the reasoning, and the short answer is that the list is shorter than a typical agency's because we removed everything we could not support properly.

The depth is in the middle. Nobody here is an expert in all seven, and pretending otherwise would be dishonest. What we do have is enough breadth to own a whole system, and enough depth in each area to know when a job needs a specialist platform and when it does not.

Yes. Learning an existing codebase is normal work and is usually faster than the client expects. The genuine question is whether the stack is still supportable, and we will say so if it is not.

It gets retired, deliberately and with a plan. The technology and innovation page describes how we decide, and the short version is that the platform is a means and the system is the thing being maintained.

Yes, and deliberately. Open source keeps the code, the hosting and the ability to change supplier available to the client, which is the whole basis of the arrangements described on the why SmartEdge page.

Where a licensed product is genuinely the right answer, for instance a specific enterprise requirement. Where an open platform does the same job, we say so rather than selling the licence, because the recurring cost is the client's.

By keeping the list short and by reviewing it rather than accumulating. Every platform we carry has to be one we can support at three in the morning, and that constraint does more to keep us current than any training budget.

Yes, and that is sometimes the most useful conversation. A short assessment before a commitment is far cheaper than a migration, and it can be arranged through the discovery call.