Skip to content
Piar Concept
Piar Concept

Frequently asked questions

Can you work on existing software?

Yes. We can contribute features, integrations and improvements to existing products. Before committing to scope, we need to review the code, architecture, environments and available documentation.

The review identifies dependencies, tests, deployment constraints and knowledge held only by the current team. It informs whether to extend the system, refactor a part or replace a component gradually.

A complete rewrite is not an entry requirement. Changes need a validation method and a delivery plan compatible with business continuity. Access to repositories and environments is coordinated with the project owner.

More questions

What does Piar Concept do?When does custom software make sense?What does software architecture contribute to a business?Can you integrate ERP, CRM and other APIs?Which internal processes can be automated?How do you approach applied AI?Do you collaborate with UX studios and consultancies?How much does a project cost and how long does it take?What do you need to assess a new project?What does Clean Architecture bring to a project?What is the Piar Turbo Template?How do we adapt the template to each business?Why use a monorepo for multiple applications?How do we organise software around business areas?How do we keep an integration from shaping the entire system?What is a BFF and when does it make sense?How do we verify business rules and integrations?How does this architecture translate into real projects?How do we prepare an MVP to evolve?
Reading guide · Markdown
Can you work on existing software?