Idepoo Services
Custom web software development
Portals, workflow automation, internal tools — when your work fits no product on the shelf. And honestly: when it does.
When custom software is worth it — and when it is not
Not worth it if a ready product solves your problem at a 90% fit; the remaining 10% is not worth ten times the cost, and we say so in the first meeting even when it costs us the job. Worth it when your process is your competitive edge and no product has it; when it must connect to three systems you already run; or when the ready product's per-user rent has grown to where owning the code pays back within two years.
Three kinds of system we build
Organisational portals — for municipalities, institutions, universities: roles, forms, workflow, archive, reporting. The Tehran District 15 municipality case is one of these. Workflow automation — request, approve, track; whatever moves on paper and in chat threads today. Internal tools — sales dashboards, inventory, support panels; the thing your team opens every day, which should be shaped exactly like your work.
How we build it
Discovery and a scope document; a clickable prototype before a line of code; development in two-week deliveries on a staging server that is always up; automated tests on the core logic; handover with code, documentation and training. .NET 10 at the back, React/Next.js at the front, SQL Server or PostgreSQL.
What you get
Scope document
Deliverables, roles and flows — the thing the price is fixed against.
Clickable prototype
See and change the main flows before development; change is cheap here.
Staging server
Something to look at from week two, more every two weeks.
Tests and security
Automated tests on core logic, authentication and role-based access, change logs.
Documentation and training
For users, and for whichever engineering team maintains the code later.
Support
A warranty period, then a support contract with a named person.
A real case
The Tehran District 15 municipality portal: public information, citizen services and forms with organisational roles and staged approval, on ASP.NET Core and SQL Server. And the Tehran cultural events platform — a multi-stage approval chain, a venue atlas on a map and geofenced field reports for all 22 districts, with web, mobile and API clients on one core.
What custom software costs
It depends on roles, processes and integrations; a typical portal or workflow system starts from 250m toman, priced from a written scope document that you approve before the contract. Staged payment follows each delivery. The price estimator gives a first range in two minutes.
Questions
How do we know a ready product is not enough?
If you must connect three systems, if your process "almost" fits and you work around it daily, or if the monthly per-user rent has become heavy. We check exactly this in the first meeting.
How long does it take?
Internal tools 6 to 10 weeks; organisational portals 3 to 6 months. A first version always ships before the full one.
Who maintains it after handover?
Either your own engineers with the documentation and code, or us under a support contract. Both are possible; you are not locked in.
Does it integrate with what we already run?
Yes; integration is usually the core of the job — accounting, ERP, attendance devices, payment gateways, SMS.
How is security handled?
Standard authentication, role-based access, encryption of sensitive data, change logs, and a security review before handover.
How do you price?
From the scope document, in stages: deposit, milestone deliveries, final settlement. No number without a scope document, because the number would mean nothing.
What is done today on paper, in spreadsheets or in chat that should not be? Write that down; we reply within one working day.