Applications.

The right "application" to solve your problem can be many things. Before writing code, I align the product type with the real pain.

• B2B SaaS — multi-tenant, billing, onboarding and analytics. Recurring revenue model from day 1.
• Internal systems — custom ERPs, CRMs, operational tools that replace messy spreadsheets.
• Dashboards and BI — data visualization for decisions. Real-time or batch, depending on the case.
• Integrations — middleware between systems, data sync, webhooks, job queues.
• Marketplaces and e-commerce — transaction platforms with payment, order management and logistics.

I choose the stack based on scope, team and deadline. A small app doesn't need Kubernetes — a big one can't be a 1-dev monolith. The focus is defensible simplicity.

Short discovery, MVP in 4-6 weeks, continuous iteration. I don't believe in 6-month closed projects without delivery — when the end comes, the market already changed.

Every release goes to production, is used by real people, and feedback feeds the next cycle. Product metrics (activation, retention, churn) are visible to the whole team.