If the program we gave you breaks, we fix it
Company software, built in Iran
We look at the work as it is.Then we write the software for it.
Letters, invoices, purchasing, stock, sales, or leave — if that still runs through chat and spreadsheets, we build the system for that path. We do not sell a ready-made app on a monthly plan. Faults in software we have delivered do not expire.
From 50M
Starting price for one process, in tomans
50 / 25 / 25
At contract, mid-build, delivery
No expiry
Fixes for that same program
After we see it
The contract price
The difference
The software fits the company. The company is not bent around an app.
A lot of what is on the market is one fixed program with a monthly fee. The company has to reshape its work to match the features. We do the opposite.
A sample of the work screen. Not a client's data.
SampleIn
Leave, sales
Supplier invoice
With someone
Parts order
This week's pay
Moving
Stock out
Done
Cost report
There is no single edition for everyone
Your approvals, departments, and the programs you already use change the design.
The price is not final before we see the work
The numbers on the site are floors. The contract amount is written after the scope is known.
Delivery is not the end of the relationship
Faults in that program are fixed for its life. A new capability has its own agreement.
What we build
Where the work gets stuck today
None of these is a ready-made subscription. If the work exists in your company, the software is arranged around your departments, people, and approvals.
01
Internal letters and requests
Following up today means calling to ask whether it arrived.
A request gets a number, reaches the right person, and you can see who is holding it.
Details→Number and log
Handoff between units
Multi-step approval
Deadlines and reminders
02
Invoices and payment requests
The invoice sits in a chat, payment is late, and the cost report is assembled by hand.
An invoice has an approval path, and a due date does not vanish.
Details→Today
Invoice log and approval
Payment requests
Due dates
Reminders
03
Sales follow-up
A customer called, and nowhere does it say when the next conversation is.
A lead has an owner. Follow-up does not depend on one person's memory.
Details→Leads and customersOpen
Owner and remindersRemind
Opportunity statusQuote
QuotesWon
StockSales says the item is there. The warehouse says it is not. The difference appears at month end.PurchasingThe purchase repeats, but every time someone has to ask who is supposed to sign.DocumentsThree copies of one contract exist, and nobody is sure which one was signed.Management reportsThe board meeting is today and the report is still being assembled.A robot for repeated workThe morning starts by copying from one screen to another, and the same mistakes repeat.Connecting the programs you already haveOne item is one quantity in sales and another quantity in the warehouse.A process base for the companyEach unit has its own method, and delays are not visible anywhere.One system for the companyThe company's core records are split across programs, and none of them covers the real process.Personnel requestsLeave was approved in a message, and payroll never heard about it.
From the request to handover
The scope is written before any code is
We do not promise a feature, a date, or a firm price before we have seen the work.
01
You write what is stuck
The company, the jammed job, and a phone number. That is enough to start.
02
We look at the work as it is
Who approves what, where it waits, and which program is already in the middle.
03
We say what to build and what to leave
Some steps should run on their own. Some still need a person. We write both down.
After delivery
If the program we gave you breaks, we fix it
This is not a few months of cover. As long as the fault belongs to the scope that was built and handed over, the clock does not run out.
This stays with us
- The program does not do the work named in the contract
- The result differs from what was accepted at handover
- A connection breaks because of an error in our program
This is new work
- A new process or capability
- A department that was outside the original scope
- An outage in SMS, a gateway, or the company's own software
- A server, domain, or license bought separately
Price
These numbers start the conversation. They are not the contract.
We do not name the contract price on the phone, before we have seen the work.
One process
From 50 million tomans
Usually up to 100 million
One clear path: a form, roles, statuses, and a compact report.
Estimate this levelOne department
From 100 million tomans
Usually up to 200 million
A few connected jobs in one unit. Sales, stock, admin, or HR.
Estimate this levelA process base or the main system
From 700 million tomans
Up past 2 billion, depending on the phase
A large job. First we have to know whether building it beats extending what you already run.
Estimate this levelHow payment works
- Half at the contract, before building starts
- A quarter at mid-build, tied to a delivery the contract names
- A quarter when handover matches the criteria that were accepted
Before you call
What people usually ask first
If the answer is not here, write it in the form or send a WhatsApp message.
What is Prociva?
A company that builds software for organizational work: admin, finance, sales, stock, purchasing, documents, HR, reports, system connections, and, when needed, robots, a process base, or one integrated system. Each project is designed for that company.
Do you sell a software subscription?
No. We do not hand the same program to every company for a monthly fee. We look at the work and write the software for it.
What does the lifetime warranty mean?
If software we built and handed over has a fault, we fix it with no time limit. A new process, a new department, and a request that was not in the contract are not part of that warranty. Response time is written in the contract.
Is the price on the site the contract price?
No. Each level is a floor for the estimate. The contract amount comes in the proposal, after the scope has been seen.
How is payment split?
Usually half at the contract, a quarter at mid-build, and a quarter at handover. The middle payment has to be tied to a named delivery, not to a vague date.
Tell us where the work is stuck
A technical brief is not required. Write how this job is done today and where it costs time or creates errors. Do not send passwords or confidential files.