ABAP development
Reports, interfaces, conversions, enhancements and forms. Code that follows the SAP standard, built not to break at the next upgrade.
Software Factory
A software factory with developers who understand your business
We allocate development squads — ABAP, Fiori, web and mobile — or deliver fixed-scope projects. Our difference is context: the same team that develops lives alongside SAP projects every day, so it understands where the data comes from.
What's included
- Dedicated squad or fixed-scope project
- ABAP, Fiori, CDS Views, integrations and Node/React
- Documented code, delivered in your own repository
- Team member replacement without stopping delivery
Which contracting model to choose
All three models work. The expensive mistake is picking the wrong model for the kind of demand you have.
| Fixed scope | Dedicated squad | Individual allocation | |
|---|---|---|---|
| How it works | Fixed price and deadline for a defined scope | An exclusive cross-functional team, with predictable monthly cost | One or more professionals embedded in your team |
| Best when | The requirement is clear and unlikely to change much | There is a continuous backlog and priorities shift often | A specific skill is missing from the internal team |
| Who manages | Avant IT | Shared | The client |
| Scope flexibility | Low: change becomes an amendment | High: repriotised every sprint | High, within the contracted skill |
| Schedule risk | Ours — the price is fixed | Shared | The client's |
What we build
Fiori and CDS Views
Fiori applications and CDS modelling to get users out of the SAP GUI. S/4HANA adoption improves a lot when the screen stops being intimidating.
Integrations
SAP CPI, PI/PO, REST APIs and file exchange. Integration is where projects usually stall — we treat it as a discipline, not a detail.
Web and mobile
React and Node applications and mobile apps consuming data from SAP or your own systems, with corporate authentication.
Portals and internal applications
Systems that replace the process currently living in a shared spreadsheet nobody knows the right version of.
Legacy modernisation
Refactoring and gradual replacement of old systems, without the big-bang strategy that almost never works.
How we avoid the classic software factory problem
The most common complaint from companies that have hired a software factory is always the same: the code arrives working, but nobody inside the company can maintain it afterwards. Documentation is missing, the style is unfamiliar, and the knowledge left with the contract.
We handle this with three contractual commitments. First, the code lives in your repository from the first commit, not in ours. Second, coding standards and peer review are mandatory — and the standard is agreed with your team, not imposed by ours. Third, every delivery includes technical documentation and, where it makes sense, a recorded knowledge transfer session.
If a squad member has to be replaced, the handover happens with an overlap we pay for. You do not lose speed because someone on our side changed projects.
How a squad starts
Understanding the backlog
A technical conversation about what needs building, the current stack and the constraints. Without it, sizing a squad is guesswork.
Composition proposal
We define how many professionals, at which seniority and for how long. An oversized squad burns budget; an undersized one delays everything.
Setup and integration
Access, environments, rituals and tools. Our team joins your team's ceremonies — we do not create a parallel process.
Sprints with demonstrable delivery
Every sprint ends with something that runs and can be seen. Burndown and velocity reports are yours, available at any time.
Frequently asked questions
What is a software factory?
It is a supplier that takes on software development in a structured, recurring way, with process, quality standards and the ability to scale the team with demand. It differs from hiring a freelancer by having a defined process and continuity — if one professional leaves, the knowledge and the delivery commitment remain.
What is the difference between a dedicated squad and fixed scope?
With fixed scope you buy an outcome: defined price and deadline for a specific delivery, with the estimation risk on us. With a dedicated squad you buy delivery capacity: an exclusive team working on your backlog, with priorities you set each sprint. Fixed scope needs stable requirements; a squad is better when priorities move.
Do you develop outside SAP?
Yes. Half of our factory works on non-SAP development: web applications, mobile, APIs and internal systems. The advantage of hiring us shows precisely in projects that need to talk to the ERP — the developer does not treat SAP as a black box.
How is code quality managed?
Mandatory peer review, coding standards agreed with the client at the start of the contract, automated tests where the context allows and static analysis in the pipeline. In ABAP we follow the ATC checks. None of this is optional or billed separately.
Can we start small and scale later?
That is the path we recommend. Most of our squads start with two or three people on a well-defined slice and grow once the working relationship is calibrated. Starting big raises the cost of a sizing mistake.
Read more about Software Factory
Fábrica de software: squad dedicado, escopo fechado ou alocação? Como escolher
Os três modelos de contratação de desenvolvimento, quem assume o risco em cada um e como escolher o formato certo para o…
Desenvolvimento ABAP: quando customizar o SAP e quando não
Toda customização SAP é uma dívida que você paga em todo upgrade. Os critérios para decidir quando ela se justifica e co…
Como escolher uma fábrica de software: 10 critérios que importam de verdade
Portfólio bonito e proposta barata dizem pouco. Dez critérios objetivos, com as perguntas exatas para fazer na reunião e…
Need development capacity?
Tell us what the backlog looks like and we return a squad composition proposal or a fixed-scope estimate — whichever fits your case better.