Custom business software development
Build Software Around
How Your Business Actually Works.
Filari designs and develops custom business applications for workflows generic software cannot handle well — ERP modules, portals, booking systems, dashboards, mobile apps and connected platforms. We understand the process first, then decide what should be built, integrated or automated.
From disconnected work
To one connected workflow
Illustrative process concepts and sample data · not client work
What do you need to build?
Start with the business problem. Then choose the software.
Seven common shapes of custom build. Open any one for the workflow, the modules and where it fits commercially.
Often the answer is one module, not a new platform.
When the process outgrows the tools
Excel wasn't designed to run your entire business.
The same information is entered several times
Once in the sheet, once in the ERP, once in an email.
Teams work from different versions
And nobody can say which one is current.
Approvals depend on phone calls
The decision exists, the record of it does not.
Customers keep asking for status
Because there is nowhere for them to look.
Reports take hours to prepare
Assembled by hand, the day before the meeting.
Data sits in separate systems
Each one correct, none of them agreeing.
Staff depend on individual knowledge
One person leaves and a process leaves with them.
Errors become hard to trace
No history, no audit, no answer.
Management cannot see the full process
Only the parts that reach a meeting.
The problem isn't always missing software.
Sometimes it is software that doesn't work together.
The same request, two processes
Same business process. Fewer manual steps.
Before
After
Nine steps became nine states.
The difference is that the system holds them.
The consulting question first
Custom doesn't mean rebuilding everything.
Before recommending development we ask whether an existing system already solves this, whether it can be integrated, whether it can be extended, or whether the workflow genuinely requires a custom application.
Buy
Mature software already solves the problem well. Buying it is the cheaper, faster and better-supported answer.
Integrate
The systems work individually, but the data does not move between them. Connect, do not replace.
Extend
An existing platform handles most of the requirement and needs one custom module beside it.
Build
The workflow, the experience or the business logic is genuinely unique — and worth owning.
"Should we build this?" — seven honest questions
Custom software is an investment. It should solve an important problem.
Discovery, roles & workflow
Before writing code, map the process.
The discovery workshop covers
What comes out of it
For large or unclear systems, discovery is a separate paid engagement — and the deliverables are yours whatever you build next.
Roles & permissions
Role decides what can be viewed, created, edited, approved, exported and what stays confidential. For complex systems, permission is action-specific rather than only role-specific.
Conditional workflow
Rules run on IF / THEN / ELSE, status, role, time, amount, location and category.
Approval chains
Every approval records who approved, when, what changed and what comment was added.
Automate repetition. Keep decisions with people.
The line we holdAutomation that hides an important business decision is not automation, it is a liability. Judgement stays visible and attributable.
WhatsApp, AI & integrations
Your custom software should not become another data island.
WhatsApp layer
Add-onWhatsApp is the conversation and notification layer. The business application remains the source of truth. Optional paid add-on.
AI where it reduces real work
OptionalAI never invents
Payment status, order status, approvals, pricing, inventory, legal decisions, clinical decisions or regulatory facts. Where risk is high, a person approves.
Integrations & API-first
Connect what works. Build what is missing.
Data, audit trail, documents & notifications
Good software starts with good data structure.
Data model
Consistent IDs, no duplicate disconnected records, and history kept wherever the business needs to explain a past decision.
Audit trail
Matters most in finance, education, healthcare, enterprise and anything with a compliance obligation.
Documents
Notifications
Do not notify people unnecessarily. Preferences where it suits the audience.
Dashboards, reporting, self-service & the field
Let people complete simple actions without calling your team.
Operations today
Sample dashboard · demo data
A dashboard should answer a management question. Reports export to PDF, Excel or CSV, and can be scheduled where that is genuinely useful.
Customer & partner self-service
Less repetitive coordination, better visibility, a faster process — and fewer calls that exist only to ask a question the system already knows.
Mobile & field operations
Where the architecture supports offline mode, data syncs when connectivity returns.
Security, privacy, scale & architecture
Security belongs in the development process.
Designed, implemented, tested and monitored — not added the week before launch.
Authentication
With MFA where the risk warrants it
Role-based access
Enforced server-side, not in the UI
Encryption
In transit and at rest
Input validation
Every boundary, every time
Session & API security
Scoped tokens, short lives
Secrets management
Never in the repository
Audit logs
Who did what, when
Backups & recovery
With a tested restore
Environment separation
Dev, staging, production
Dependency management
Tracked and updated
Secure deployment
Reviewed and repeatable
Vulnerability handling
A named process
Standards we work against
Secure-development guidance appropriate to the system risk — OWASP ASVS and the NIST Secure Software Development Framework. We do not claim any system is "100% secure": security is an ongoing engineering discipline, not a launch checkbox.
Privacy & data control
Consent, data minimisation, retention, export, deletion, access control, sensitive-data segregation and audit. Requirements vary by industry, country, data type and how you operate — they are determined during discovery. Security features alone never mean automatic compliance.
Scale, honestly
Architecture accounts for realistic concurrent users, daily transactions, file storage, API calls, reports, geography and growth. We do not over-engineer a twenty-user internal tool for millions, and we do not under-engineer a mission-critical public platform.
Modular architecture
Clear modules that can evolve independently — without automatically reaching for microservices. The architecture follows the actual scale and the size of the team maintaining it.
Build for the scale you can reasonably expect — with room to grow.
How we work
From process map to production software.
01
Discovery
The business problem
02
Process mapping
Current and desired workflow
03
Scope
MVP plus roadmap
04
UX / prototype
Screens and roles
05
Architecture
Data, integrations, security
06
Development
Iterative modules
07
QA
Functional, role, integration, security
08
UAT
The business team validates the workflow
09
Deployment
Production
10
Training
Users and admins
11
Monitor
Issues and performance
12
Improve
Future releases
Start with the core workflow
Launch the useful system first. Expand based on real usage.
Migration
Replacing Excel, a legacy system or an old database. We do not promise a perfect migration until the source data has actually been assessed.
Testing, monitoring & support
In production: error and uptime monitoring, logs, verified backups, performance, security and dependency updates, support and incident response. Custom-software maintenance is not website care — it is quoted against criticality and SLA.
Industry workflows
The same architecture, a very different process.
Education
Enquiry → application → admission → student
View industry page →Healthcare
Appointment → patient journey
View industry page →Travel
Enquiry → itinerary → booking → operations
View industry page →Real estate
Lead → site visit → booking
View industry page →Manufacturing
RFQ → quote → order → service
View industry page →Professional services
Enquiry → consultation → client workflow
View industry page →E-commerce
Order → payment → fulfilment
View industry page →Sample systems
Different workflows. Different software.
Open any system to walk through its user view, dashboard, workflow, mobile screen, admin and reporting.
Illustrative system concepts built for this page · clearly labelled sample data · not client work
Investment
Custom software is priced around scope — not screens alone.
Final cost depends on business logic, user roles, modules, data, integrations, automation, security, reporting, mobile apps, migration and scale. These are indicative ranges, not fixed quotations.
Focused custom module
₹1,50,000+
One well-defined workflow
Custom business application
₹3,00,000+
A core system with several roles
Advanced portal / operations platform
₹5,00,000+ / custom
Multi-module, multi-audience
Large / enterprise platform
Custom discovery
Multi-department, high volume
Before a large build
Software discovery workshop
For large or unclear systems, discovery is a separate paid engagement — and the deliverables belong to you whatever you decide to build next.
Ownership, stated clearly
Clear ownership from the start.
You may own
Custom business code, business data, provided content and the project-specific database schema — per the agreement
Third-party components
Open-source and licensed components remain subject to their own licences
Filari IP
Reusable frameworks, SaaS platforms and proprietary products remain Filari intellectual property unless expressly transferred
Never blurred
Custom development and Filari SaaS products are two different things, priced and owned differently
Optional add-ons
Provider, API and usage fees remain separate.
Custom build, or Filari CRM?
If you need contacts, leads, follow-ups, tasks and a basic pipeline, we use or extend Filari CRM. We do not build a separate CRM for every client. Custom development starts where the workflow, the entities or the industry operations are genuinely beyond what a CRM should be asked to hold.
Don't build a CRM for every client. Build the business process a CRM alone cannot handle.
Why Filari
We don't start with features. We start with the process.
Process first
Understand how the work actually happens, including the exceptions.
Modular build
Build the important pieces first and prove them in real use.
Connect existing systems
Do not rebuild what already works well.
Automate repetition
Reduce coordination that exists only because tools do not talk.
Humans keep control
Important decisions stay visible and attributable.
Grow over time
Add modules once usage proves the need, not before.
Questions
What businesses ask before commissioning software.
Twenty-one answers on scope, cost, what can be built, integration, data, AI, ownership and maintenance.
Scope & approach
01What is custom software?
An application designed around a specific organisation — its workflows, users and business rules — rather than a standard mass-market product.
02When should we build custom software?
When existing products cannot support an important workflow without significant compromise, or when connecting and automating the process creates substantial business value.
03Should we build everything from scratch?
Usually not. We first evaluate whether existing software should be retained, integrated, extended or replaced — buy, integrate, extend, build, in that order of preference.
04How long does development take?
It depends on scope, integrations, migration, security and testing. Complex software is delivered in controlled phases rather than against an arbitrary rapid deadline.
05How much does custom software cost?
Focused custom modules can start around ₹1.5 lakh. Broader business applications and platforms require discovery and scope-based pricing.
What can be built
06Can you build only one ERP module?
Yes. A custom module can be developed and integrated with the existing system where its APIs and architecture support it.
07Can you build a customer portal?
Yes — with role-based access, documents, payments, requests and self-service.
08Can you build a vendor, dealer or partner portal?
Yes. Each partner sees only their own accounts, orders, documents and commercial terms.
09Can you build booking software?
Yes. Booking can support availability, capacity, waitlists, deposits, cancellation, rescheduling and other business-specific rules.
10Can you build an internal approval system?
Yes — single, multi-level, parallel, conditional, amount-based and department approvals, with escalation, delegation and a full audit trail.
11Can multiple departments use the same system?
Yes, with role and action-specific permissions so each department sees and does only what it should.
Integration, data & AI
12Can custom software integrate with our existing ERP?
Potentially. It depends on the existing platform exposing APIs, the permissions available and the technical architecture — which we verify before promising anything.
13Can WhatsApp be connected?
Yes, as an optional automation add-on. WhatsApp is the conversation and notification layer; the application remains the source of truth.
14Can AI agents be added later?
Yes, where there is a clear use case and a reliable data source. AI never generates payment status, approvals, pricing, inventory or regulated facts.
15Can existing data be migrated?
Yes, after assessing the structure and quality of the source. We do not promise a perfect migration before seeing the data.
16Can we add a mobile app later?
Yes, provided the architecture is planned for it — which is why API-first design matters from the first release.
17Can the system be expanded later?
That is the point of modular architecture. Phase one proves the core workflow; later phases add automation, portals, AI and analytics.
Commercials & ownership
18Who owns the source code?
Ownership and licensing are defined in the project agreement. Custom project code may transfer per agreed terms, while third-party components and Filari-owned reusable products remain subject to their own licences and IP terms.
19Can Filari maintain the software after launch?
Yes, through an agreed maintenance and support scope. Custom-software maintenance is quoted against system criticality and SLA — it is not the same as website care.
20Is this the same as Filari CRM?
No. If you need contacts, leads, follow-ups and a basic pipeline, we use or extend Filari CRM. Custom development starts where the workflow genuinely exceeds what a CRM should hold.
21Do you guarantee an outcome?
We commit to the scope, the process and the engineering standards. Business outcomes depend on adoption, data quality, process discipline and how the organisation uses the system.
When generic software stops fitting
Show us the process.
We'll help determine what should be built.
You may need a new application, one custom module, an integration — or simply a better workflow. The first step is understanding the business problem before choosing the technology.
Don't build more software.
Build a better process.