What We Build on Symfony
- enterprise systems for tracking and approvals: requests, contracts, invoices, document routing between departments, with access rights and change history;
- partner and dealer portals with individual terms, orders and reports;
- multi-role portals where data for different user groups is strictly separated;
- a centralized API that feeds the website, mobile app and accounting systems, documented and versioned;
- components of ERP solutions that extend off-the-shelf accounting systems to fit a company's specifics;
- integrations with QuickBooks, SAP, CRMs, banks and shipping carriers, with heavy jobs such as imports, reports and sync run in queues.
Symfony or Laravel, and When Neither
Both frameworks are reliable PHP options, so the choice depends on the project:
- Laravel fits when you need a first version fast, want to validate an idea, and the team is small.
- Symfony fits when the system is large from day one, several teams will work on it and the lifespan is measured in years.
- If you already have a team that knows one of the frameworks, that is often a stronger argument than the technical differences.
- For a site that is mostly text and pages, you need neither: a CMS is more convenient.
The trade-offs of Symfony: a slower start than Laravel because more configuration is needed up front, a higher bar for developers, and no ready-made content admin panel, so the interface for your staff is built around the system.
New Project or Existing System
A new project starts with the data model and module boundaries. This stage decides how easy the system will be to evolve years from now, so we agree on the structure with you before development. An existing system often runs on an old Symfony version that no longer gets updates. Rewriting everything is risky and expensive, so we cover key scenarios with tests and upgrade in parts, version by version and module by module. Learn more on our legacy system modernization page.
How We Keep Code Quality
- key scenarios such as payments, calculations and access rights are covered by automated tests that run on every change;
- every change is reviewed by another developer before it reaches the shared codebase;
- automated code analysis catches common errors before human testing;
- important architectural decisions are documented, so newcomers know what was decided and why.
As the system grows, we help with caching, database query optimization and load balancing, and after launch we handle updates, error monitoring and new features.
What We Need from You
- A description of your business domain: entities, rules and exceptions.
- The user groups and what each can see and do.
- Documentation for the systems to integrate.
- For existing systems: repository access, the Symfony version and any documentation.
What Affects Cost and Timeline
- Business domain: the number of entities, rules and exceptions.
- Roles and access: how many user groups and how granular their permissions.
- Integrations: the number of systems, whether they have a documented API, and exchange speed.
- Load: how many people and requests the system handles at once.
- Existing code: Symfony version, tests, documentation.
We estimate large systems in phases: first design with a detailed plan, then development in parts, with visible results after each one.
Frequently asked questions
Can we gradually move from custom PHP code to Symfony? Yes. Symfony components can be introduced into existing code piece by piece without taking the system offline.
Our system runs on an old Symfony version. Is that critical? An old version without security updates is a risk. We assess its condition and propose an upgrade plan with minimal disruption.
Is Symfony a good fit for an online store? For a standard store, no, an established platform is better. For B2B commerce with complex terms and integrations, yes.
How many developers does it take to maintain a system like this? It depends on the pace of change. A stable system often needs only scheduled updates and small enhancements, while for active development we put together a dedicated team around your roadmap.
Who can maintain the system if we switch vendors? Any team that knows Symfony. We hand over the code, access and documentation, and the framework's standard structure makes the handoff easier.
Do you give an estimate before development starts? Yes. For large systems we begin with a design phase and a detailed plan, then estimate development by phase.
Why Promodex
We do not push Symfony: if the task can be solved more simply, we say so on the first call. Promodex has been in business since 2015, with 750+ completed projects and an in-house team of 30+ people. We do not outsource, so knowledge about your system stays within the team, and for long-term projects we agree on a transparent way of working and stay with you after launch.