Pricient — by IOanyT
Describe the project. Leave with the documents.
Defined by both lists — every quote comes with what it includes and what it doesn't, both written down. See both lists
A specification, wireframes and an itemized quote. No callback, no discovery call.
Or start from one of these —
No signature, no call. A business email unlocks the full quote.
now The self-serve intake is being finished. Until it opens, a person runs it with you by email — same questions, same documents, same price lock.
- REQ-014 Users sign in with email and password, with rate-limited retries High
- REQ-015 Sessions expire after 30 days of inactivity High
- REQ-016 Failed payments retry twice, then notify the account owner Medium
- REQ-017 Admins export the member list as CSV High
Confidence is stated per requirement, and the quote says where scope is still uncertain.
Rendered as images in the free set. The editable files arrive on signature.
- Authentication & user management
- Payments — Stripe
- Admin console
- Test coverage 80%+ Included
- Security review — OWASP Included
- Audit-ready documentation Included
Every line traces back to a requirement. Change one and the quote updates.
The features that usually ride along unspoken — listed, with a backlog price each.
- Multi-language backlog
- Data exports beyond CSV backlog
- SSO / SAML backlog
- Push notifications backlog
- Offline mode backlog
The quote is defined by both lists. This is the single biggest cause of disputes, removed.
- ISO 9001:2015
- ISO/IEC 27001:2022
- AWS Advanced Partner
- 10+ years
- IOanyT is a member of Nasscom
Unpriced
The thing you stopped asking about
Most projects do not die because someone said no. They die because nobody would put a number on them — so they stay on a whiteboard, and everyone works around them instead.
-
The spreadsheet that quietly became a system
Four people maintain it, one of them is leaving, and no one can describe it well enough to get it quoted.
Price this one -
Two systems that have never spoken
Someone re-keys data between them every week. Every estimate came back as "it depends on the API".
Price this one -
The three days every month-end eats
Everyone knows the steps. Nobody has written them down, so nobody will price the fix.
Price this one -
The customer portal that has been next quarter for two years
The scope grows every time it is discussed, so the discussion keeps getting postponed.
Price this one -
The report someone assembles by hand for the board
It is too small to be a project and too painful to leave alone.
Price this one -
The AI pilot that never reached production
It answered well on curated data. Then it met the real systems, the real permissions and the question of who signs off.
Price this one -
The screen nobody will touch
It works. No one still here knows why. Every quote assumed months of working that out first.
Price this one -
A review queue that never gets shorter
Every case gets read by a person, most of them did not need to be, and nobody can say which.
Quote a Diagnostic -
The triage step everyone does slightly differently
Two people sort the same case into different piles. The rule exists; it is just not written anywhere.
Quote a Diagnostic -
An eligibility or onboarding check that takes days
The criteria fit on one page. Applying them takes a week of email.
Quote a Diagnostic
None of these needs a written brief to start. Describe it the way you would say it out loud, and the questions come back to you.
01 / 03 The idea you cannot quite write down
A sentence in. A traced specification out.
It reads what you meant, not only what you typed.
What you write
“we need a booking thing for our clinic — patients pick a slot, we take payment, and it has to work with our records system”
32 words · no structure · no scope
What comes back
- REQ-001 Patients browse available slots by practitioner and date High
- REQ-002 Card payment taken at the point of booking High
- REQ-003 Two-way sync with the existing records system Low
Caught, unprompted
- Healthcare — HIPAA pack loaded
- Card payments — PCI controls added
- "works with our records system" — Which system? Does it have an API?
REQ-003 still uncertain → said so in writing, not guessed
The difference
Same question, two experiences
The usual route to a price
~2 weeks- Contact form
- Callback
- Discovery call
- Internal estimating
- PDF, one number
One number, and no list of what it leaves out.
Asking Pricient
no callDescribe it Questions back Scope agreed Spec + quote
A fixed, itemised quote with exclusions, before any call.
02 / 03 Nothing hidden
Everything it includes. And everything it does not.
Disputes come from the list nobody wrote down. So we write it down.
In this release
priced- Authentication & user management
- Payments — Stripe
- Admin console
- Member CSV export
Not in this release
backlog- Multi-language
- SSO / SAML
- Push notifications
- Offline mode
- Bulk import
Each one carries a backlog price, so adding it later is a number rather than a negotiation.
That is what "Defined by both lists" means. The price covers the first list. The second is written down so nothing is left to assumption — the usual start of every "I thought that was included."
Every assumption is written down too. If one turns out to be wrong, that is a pre-agreed trigger to re-quote — not an argument six weeks in.
03 / 03 Yours either way
Finding out costs you nothing
No signature to see it. No call to get it.
Nothing
The specification and the quote are free.
No call needed
Nothing to prepare beforehand.
No commitment
The documents are yours either way.
Your price is locked for 14 days. If you build it elsewhere, the Portable Spec Pack travels with you — credited in full if you come back.
Wherever you are starting from
A decision about a workflow
Which steps to automate, which to keep on an AI model, which to leave alone, decided before anyone builds.
Workflow DiagnosticA system nobody can read
Fifteen years old, undocumented, the people who wrote it gone — and the business still runs on it.
Legacy modernizationAn AI pilot that stalled
Copilot, Agentforce, Bedrock or a RAG build that worked in the demo and never reached production.
AI pilot rescueA prototype that broke
Built on Lovable, Bolt or v0, now facing real users, real data or a real auditor.
Prototype rescueAn idea, and not much else
No website, no company email. The path switches rather than stopping.
For foundersEverything else you would ask
-
How does it actually work?
Describe it, get the documents
-
What exactly do I receive?
Free set and signed set, item by item
-
How is the price arrived at?
Three tiers, every line visible
-
Is the work any good?
Audit-ready by default, never self-certified
-
What happens after I sign?
Every requirement traced to acceptance
-
What if I build elsewhere?
The pack travels, credited in full
Defined by both lists
Describe your project. See what comes back.
No signature, no call. A business email unlocks the full quote.