Custom software: what to build, when, and how not to waste money
Guides on CRM, ERP, portals, internal panels, ecommerce, and integrations — with clear deliverables, not consultancy presentations.
Priority guides for custom software
Full stack development
How to approach a complete web application: backend, frontend, data, and integrations with a closed scope.
Custom CRM
Pipeline, activities, and reporting tailored to your sales process — without paying for 200 features you don't use.
Custom ERP
Stock, purchases, production, or logistics in a system that truly reflects how you work.
Replace Excel
When an Excel can no longer hold up and what software to build to stop copying data manually.
API integrations
Connect CRM, ERP, ecommerce, accounting, and tools without duplicating information.
Custom ecommerce
Online store with catalog, orders, stock, and custom business rules — beyond a template.
The problem: generic software that doesn't fit
Many companies end up with a CRM that the sales team doesn't use, an ERP that's too rigid, five conflicting Excels, and an ecommerce system that doesn't communicate with the warehouse. The issue is usually not a 'lack of software', but software that doesn't reflect how you work.
Buying user licenses, activating modules that no one requested, or contracting development without a closed scope often leads to frustration: extended deadlines, exploding costs, and a system that only one person in the IT department uses.
Custom software is not synonymous with 'building everything from scratch'. It's about designing a system that covers your critical processes, integrates with what you already have, and can be maintained without relying on a single vendor who might disappear or raise prices every year.
At RUMAZA, we see the same pattern: companies with real operations (B2B orders, stock in multiple warehouses, unusual commissions, scattered documentation) trying to fit into tools designed for another sector. The result is manual work, errors, and zero visibility for management.
The real cost doesn't appear on the SaaS invoice. It shows up in the salesperson who takes 40 minutes per order, in the stockouts that no one saw coming, in the corrective invoice due to transcription errors, and in the founder who can't delegate because 'everything is in my head and in an Excel'. That doesn't scale.
It also doesn't get fixed by hiring 'a development' without an internal product owner, acceptance criteria, and milestones. We've inherited half-finished projects: undocumented code, manual deployments, and a business team that distrusts any new screen. Well-executed custom software starts small, demonstrates value, and grows with clean data.
This library contains guides on the topics we get asked about the most: full stack development, CRM, ERP, internal panels, B2B portals, ecommerce, integrations, and replacing Excel. It's not a service catalog; it's a criterion for deciding what to build first and what isn't worth it.
If you're looking for a quick answer: start with the process that costs you the most money or time today, measure the cost of the status quo, and build a small milestone with clear success criteria. The rest of the hub delves into each piece.
Explore the priority guides in the hub if you're looking to dive deeper into a specific topic. Each one has between 1,800 and 2,200 words focused on decision-making: problem, when to act, what to build, how we would do it at RUMAZA, common mistakes, and questions we get in real calls.
What is custom software (in plain terms)
It's software built to solve specific processes in your company: managing clients, orders, stock, documents, B2B portals, or internal panels. It can be a web application, an API, an admin panel, or a combination of all of that.
Custom doesn't mean reinventing Gmail. It means that the flow of 'client requests → sales validates → warehouse prepares → invoicing issues' is modeled as you do it, with permissions, alerts, and reporting that matter to management.
We build it in layers: well-modeled database, backend with business rules, usable frontend, and when necessary, integrations with ERP, payment gateways, carriers, or AI. Each piece has a verifiable deliverable.
The alternative — continuing to park the problem with more spreadsheets or more licenses — has a hidden cost: team hours, errors in orders, poorly served clients, and decisions made with data from three weeks ago.
We also don't confuse custom with 'programming whatever the committee says'. First, we understand the process, trim the unnecessary, and deliver something that the operations team uses on Monday morning. The code is yours; the business knowledge is yours; we translate that into a system with realistic maintenance.
You can read the guides in any order, but we recommend the hub if you're still unclear whether you need a CRM, ERP, panel, or integration. Each guide links to related pages on software, data, and AI when the next natural step crosses domains.
The guides in this hub are updated with frequently asked questions from real projects. If something isn't covered, there is likely another page in the software hub (37 guides) or intersections with data and AI — we link where the next step is natural.
When it makes sense to invest in custom software
- Your process is specific and no SaaS covers it without absurd workarounds
- You've been maintaining the company with critical Excels for years and they are already failing
- You need a B2B portal, intranet, or panel that unifies several systems
- You want to integrate CRM, stock, ecommerce, and accounting without manually copying data
- A standard CRM or ERP forces you to change how you sell or operate
- You need traceability, role-based permissions, and auditing that generic tools don't provide
- You have your own APIs or data and want a business layer on top
- You're looking for a digital asset that is yours, not an eternal rental of licenses
- The operations team spends more than 10 hours a week on tasks that a panel could automate
- You have B2B clients asking for a portal, API, or integration and can't offer it with the current setup
- Seasonality forces you to scale manual processes every year instead of systematizing once
- You want to document the decision criteria before investing — this hub guide helps you compare options
What can be built
Custom CRM and sales management
Pipeline, activities, commissions, alerts, and reporting aligned with your sales team — connected to email or WhatsApp if needed. Includes permissions, basic auditing, and documentation for the team to adopt it without relying on the consultant.
Operational ERP (stock, purchases, production)
Inventory movements, purchase orders, traceability by batch or location, and dashboards for operations. Includes permissions, basic auditing, and documentation for the team to adopt it without relying on the consultant.
B2B portals and client areas
Catalog with client-specific pricing, recurring orders, invoice downloads, and shipping status without calling. Includes permissions, basic auditing, and documentation for the team to adopt it without relying on the consultant.
Internal panels and lightweight intranet
A single site to consult KPIs, tasks, documents, and forms — without navigating ten tools. Includes permissions, basic auditing, and documentation for the team to adopt it without relying on the consultant.
Ecommerce with custom rules
Catalog, checkout, stock, promotions, and logistics integrated with your back office. Includes permissions, basic auditing, and documentation for the team to adopt it without relying on the consultant.
Integrations and APIs
Bidirectional synchronization between systems, webhooks, queues, and error monitoring. Includes permissions, basic auditing, and documentation for the team to adopt it without relying on the consultant.
How RUMAZA would build it
Possible technologies
- Python (Django / FastAPI)
- Next.js / React
- PostgreSQL
- Redis / Celery
- REST APIs and webhooks
- Shopify / WooCommerce (when applicable)
- Docker and deployment on cloud or VPS
Hypothetical application scenarios
The entire business in shared Excel
Orders, stock, clients, or projects in sheets that conflict between departments. A common first step: a panel or module that centralizes a critical flow.
Generic SaaS patched with macros
Standard tool at 60% and the rest in manual processes. Fits custom software in the differential core, not replacing everything at once.
Growth without a supporting system
More clients, more references, and more people using the same Excel from years ago. It's advisable to digitize in phases with a closed scope.
Common mistakes
- Requesting 'a complete ERP' in the first phase without prioritizing processes
- Copying screens from a famous SaaS without modeling your data
- Not defining who validates requirements or acceptance criteria
- Ignoring historical data migration until the end of the project
- Building without a maintenance plan or documentation
- Choosing technology based on trends rather than team and long-term
- Not measuring adoption: software that no one uses is wasted money
- Reading guides without involving those who suffer the process day-to-day — the solution will fail in adoption
- Comparing custom software budgets without comparing scope and deliverables for each milestone
Frequently asked questions
Custom software or standard SaaS?
SaaS if your process fits 80% or more and you don't need deep integrations. Custom when the process is the asset, rules are specific, or you've been patching generic tools for years. Sometimes the answer is hybrid: SaaS for the standard and development for the differential core.
How much does a custom CRM or ERP cost?
A scoped module (for example, sales pipeline + reporting) usually ranges from €5,000 to €15,000. A broader operational ERP is budgeted in phases after diagnosis. We prefer milestones with usable deliverables over a closed twelve-month project with nothing in production.
How long does the first deliverable take?
Between 4 and 8 weeks for an MVP with a main flow in production, depending on integrations and data quality. Subsequent milestones are planned with what we've learned from the first. We evaluate it on a case-by-case basis during the initial diagnosis without commitment to a closed project.
Can I start by replacing just one Excel?
Yes, and often it's the best way to start. A panel that centralizes what is currently in a critical sheet demonstrates value quickly and defines the data model for what comes next. We evaluate it on a case-by-case basis during the initial diagnosis without commitment to a closed project.
Who owns the code?
You do. We deliver the repository, documentation, and deployment. No vendor lock-ins or mandatory user licenses for the built software. We evaluate it on a case-by-case basis during the initial diagnosis without commitment to a closed project.
And maintenance?
All software needs maintenance: security, bugs, changes in external APIs, and improvements. We agree on a clear regime (hours or retainer) or train your team if you have internal capacity. We evaluate it on a case-by-case basis during the initial diagnosis without commitment to a closed project.
Can I combine SaaS and custom development?
Yes, and it often makes sense: Holded or similar for accounting, Shopify for a simple catalog, and development for the operational core or B2B portal. The important thing is to define which system owns each piece of data and avoid duplication.
What do I need to have prepared before starting?
You don't need a perfect document. It helps to have: a person who knows the process, access to sample data (Excel, exports, APIs), and clarity on what hurts the most today. In 48–72h of diagnosis, we can ground it.
Where do I start if I have multiple problems at once?
Prioritize one with a clear internal owner and measurable pain this week. It’s usually a critical Excel, B2B orders without a portal, or an abandoned CRM. A first milestone of 4–8 weeks unlocks the next with cleaner data.
What concrete deliverables do I receive in each phase?
In each milestone: code in your repository, staging environment for testing, deployment and usage documentation, and signed acceptance criteria before going into production. We don't just deliver a ZIP or an 80-page PDF that no one reads. The deliverable must be usable by someone other than the developer.
Do you work with internal teams or only external?
Both. If you have a technical person, we integrate into your workflow (Git, tickets, reviews). If not, we take on the complete operation but leave documentation so you aren't held hostage. We recommend at least one business representative to validate each sprint.
How does this library fit with software consultancy?
These guides are the criteria we apply before budgeting. If after reading them you see that your case fits into 'replacing Excel' or 'B2B portal', the conversation starts with common vocabulary and realistic expectations. If you don't fit, we'll tell you before proposing a project.
Does RUMAZA only develop or also maintain?
Both. We build and maintain what we deliver: security, bugs, changes in external APIs, and evolutionary improvements. Software without maintenance deteriorates; we plan for it from the initial budget with transparency in hours or retainer.
How are permissions and security managed?
Roles defined from the MVP: who sees, who edits, who approves. Authentication with email/password or SSO if you already use it. Sensitive data encrypted in transit, automatic backups, and logs of critical actions. It's not paranoia: it's to prevent an intern from exporting the entire client database unintentionally.
Do you offer training to the team?
Yes, a practical session of 1–2 hours on the delivered flow, plus brief documentation with screenshots. We prefer training on the real MVP, not on 50 functions that will come in phase 2. If support is needed in the first weeks, it's agreed upon as post-launch support.
Related guides
Do you need software that fits your operations?
Tell me the process and I'll tell you what I would build first — no fluff.