RightABA · Modernization
~6×
faster · ~20× less effort
A 33,000-line legacy platform with no tests, migrated to a modern architecture: 9 modules, ≥ 80% test coverage and automated deployment.
Is2Be Software · Spec-First method
Build software with AI, specifying before you code.
From where you start (as-is: the current system, or just the idea if you start from scratch) to the software you need (to-be): 7 phases and 27 deliverables: requirements, architecture, code, review, tests, deployment and monitoring. With any stack and any AI assistant.
Is2Be Software
€290/year · equals 10 monthsor €29/month, no commitment
Buy Is2Be SoftwareUse on client projects included · Better the complete pack?
What it is for
Four ways of working, one method.
The kit identifies your case and uses only the steps you need.
New project
From idea to first deployment.
Modernize a legacy system
Without losing the business rules that only live in the code.
New module
In an existing system, following its patterns.
Grow piece by piece
A new, independent piece that joins your system without putting the rest at risk.
The proof
Real projects built with this method.
Norte · New product
~3×
faster, all the way to production
An AI training platform: three apps (athletes, coach and admin), API, watch app and payments.
Norte H · App on an existing system
>10×
faster
A web and mobile app of about 31,000 lines and 264 tests, from requirements to code review with fixes.
The method creator's own projects. Timelines "without the method" are the author's estimates based on each project's scope.
Phases and deliverables
What you get at each phase.
PHASE 01
Ideation
What needs to be built.
Product requirements (PRD) with channels and non-functional requirements, with interview mode if the starting point is thin · User stories with acceptance criteria · Acceptance scenarios with the expected result of every rule
PHASE 02
Design
How it will be built.
Current system documentation · Architectures compared after asking you what is missing, at the detail your project needs · Recorded architecture decisions · Build or migration plan · Test plan
PHASE 03
Development
The code, with its tests.
Backend modules with the chosen internal architecture · Web or mobile app screens · Change audit trail · New entities in existing systems
PHASE 04
Review
Quality before merging.
Code review of every change against quality and security criteria and the PRD rules
PHASE 05
Testing
Every business rule, tested.
Test setup · Unit · API and integration · Components · End to end, also on mobile emulators or devices
PHASE 06
DevOps
From commit to production.
Continuous integration pipeline · Deployment pipeline with infrastructure as code, app store publishing for mobile and a documented rollback
PHASE 07
Monitoring
Know what's happening and how to fix it.
Structured logs · Incident runbooks
Rules that are never skipped
AI speed doesn't eat into quality.
- Phase 1 is completed for the whole scope before designing.
- No code without an approved build plan and test plan.
- Tests are written with each module, not afterwards.
- Continuous integration is set up before the first business module.
- In a modernization, the business rules of the existing system are preserved exactly, unless the business decides otherwise.
With any technology
Stack-agnostic.
The language, framework, database and platform are chosen in your project's architecture decisions. The method assumes none of them.
From process to software
Does the software come from a business process?
Start with Is2Be Process: its last step produces the briefing the requirements start from. That way the code solves the right problem.
Who it is for
For teams that already code with AI and want to do it right.
- Agencies and software factories. More margin on every project, the same quality across the team.
- Scaling startups. Scale the team without scaling the chaos.
- Freelance developers. Deliver like a team, working alone.
- IT teams with legacy systems. Modernize with less risk.