How we kick off a project in 30 days without months of meetings
At VTH Software we use a 30-day approach to go from idea to a clear technical plan with priorities and validated architecture decisions.
Read post →How we kick off a project in 30 days without months of meetings
Starting a large project can be scary: too many ideas, little time, and pressure to “launch fast.” At VTH Software we use a 30-day scheme to put order into all that without slowing the business down.
What we do in those 30 days
- Quick diagnosis: understand company context, key processes, and technical constraints.
- Domain map: identify core modules (sales, production, finance, etc.).
- Architecture decisions: monolith vs microservices, databases, cloud strategy, and security.
- Delivery roadmap: define what to build first and what the business can expect at each stage.
The outcome is a technical blueprint any team can implement—yours, ours, or mixed. No empty promises—just a concrete, prioritized plan.
Case study: organizing a food factory’s ERP step by step
We worked with an artisanal food company that needed more than “an invoicing system.” The real problem was coordinating production, inventory, points of sale, and finance without losing traceability.
Our approach
- Clear domains — Separating Production, Purchasing, Logistics, POS, Finance, and HR helped avoid a chaotic ERP.
- Architecture ready to scale — We designed an architecture based on microservices, events, and appropriate databases (PostgreSQL, MongoDB, Redis), thinking ahead to a SaaS model and franchises.
- Cloud with cost focus — We planned the AWS deployment (containers, storage, security) while controlling monthly costs from day one.
The result: an ERP that can start as an internal MVP and grow to multiple locations and franchises without rewriting everything from scratch.
Why we ask for tests from day one (even if the project is small)
When we mention automated testing many think it’s “expensive” or “only for large companies.” In practice, tests are the cheapest way to avoid regressions and rework.
What types of tests we use
- Unit tests: validate small pieces (functions, components) and prevent obvious mistakes.
- E2E (end-to-end): simulate a real user journey (e.g., create an order and charge it).
- Accessibility & performance checks: ensure the site not only “works,” but is usable and fast.
What your project gains
- Fewer production bugs.
- More predictable deliveries (what’s tested, works).
- Teams can move faster without fear of breaking what’s already done.
Our goal isn’t “testing for sport,” it’s protecting the budget and the project timeline.