Questions
Questions we get asked
The things worth knowing before you send an enquiry — what it costs, who owns what, what happens to your data, and where we stop.
Working together
- How does an engagement start?
- With a short, paid discovery. We watch how the process actually runs — not how the process document says it runs — and hand back a map of it, an architecture, and a costed plan for building it.
- You keep that plan whether or not you continue with us, including if you take it to someone else. It is written to be useful on its own rather than as a sales document that only makes sense if we do the work.
- What does it cost?
- We have not published rates, and we are not going to invent a range to fill this answer. What we can tell you is the shape: discovery is a fixed fee agreed before it starts, and the build that may follow is scoped and priced from what discovery found rather than estimated from a conversation.
- That means you know the cost of the next step before you commit to it, and you are never asked to approve a number that was guessed at. Ask us directly and you will get a figure for your specific situation.
- What do you need from us?
- Time with the people who do the work, which is the expensive part and the part that decides whether the result is any good. Usually a few hours across the discovery.
- Access comes later and only to what is needed. Plenty of discovery happens on screenshots, exports and conversation before anything is connected to a live system.
- How long does it take?
- Discovery is short — days rather than weeks. We will not put a number on the build here, because a timescale quoted before anyone has seen the process is a guess dressed as a commitment.
- What we will commit to is the rhythm: work ships in short increments with something you can look at at the end of each one, rather than disappearing for a quarter and returning with a reveal.
- What if the answer is that we should not automate this?
- Then that is what the discovery says, and you have paid for a clear answer rather than a build that never pays for itself. It happens, and it is a better outcome than the alternative.
- The automation finder on this site does the same thing in miniature: it will tell you when a process is not worth automating yet.
Ownership and lock-in
- Who owns the code?
- You do, from day one. Source code, infrastructure accounts, pipelines and documentation are yours, in your repositories, under your licence.
- There is no version of this where the thing we built for you stops working because you stopped paying us.
- Are we locked into you?
- No, and the handover is part of the work rather than a favour at the end. Documented, in your accounts, buildable by another team.
- This is a deliberate commercial position. A new company with no track record is asking for trust it has not earned yet, and removing the risk of being stuck is the most concrete way to reduce what a client is actually gambling.
- Do you replace our existing systems?
- Almost never, and we will usually argue against it. Migrations consume a year and a great deal of goodwill, and the cost is dominated by data history and retraining rather than by licences.
- The software most businesses run mostly works. What fails is the space between it, and that gap is cheaper to fix and less disruptive to live with.
For staffing firms
- Do you compete with us?
- No. We are a software company, not a staffing firm. We do not source, submit or place candidates, we run no desk of our own, and we will never compete with you for a placement or a client.
- That is a deliberate limit rather than something we have simply not got around to. It is what makes it reasonable to let us near your candidate database, and it is stated on the staffing page for the same reason.
- Do we have to move off our ATS?
- No. We build around Bullhorn, JobDiva, Ceipal or whatever you already run. Your ATS holds years of history and every recruiter's habits are built on it.
- Building alongside it also keeps the blast radius small: if a piece of automation is wrong, you switch it off and the desk carries on.
- Will your software reject candidates automatically?
- No, and nothing we build will. Software is genuinely good at reading every CV against every requirement without getting tired at application forty. It is not good at deciding what a gap means about a person, and that decision carries consequences for somebody's livelihood.
- Our screening example demonstrates the distinction: it produces evidence, an explained score and the questions worth asking, and it never removes anyone from the pile.
Data and security
- What happens to our data?
- It stays yours, and we take the minimum needed to do the work. Where a process can be understood from anonymised samples, that is what we ask for.
- How this website itself handles data is set out in the privacy policy, including the complete list of third parties involved — which for reading the site is our hosting provider and nobody else.
- Do you sign NDAs?
- Yes, and we would expect to before seeing anything sensitive. Send yours, or ask and we will send ours.
- Do you send our data to an AI model?
- Only where that is the point of the work, and only with it agreed in advance and written down — which document types, which provider, what is retained.
- A great deal of what we build involves no model at all. Matching, routing, reconciliation and approval rules should be deterministic and checkable, and using a model where a rule would do makes a system harder to trust and harder to debug.
About the company
- How big are you?
- Small, and new. Twishiv Platforms Private Limited was incorporated in April 2026 and is based in Vadodara, Gujarat.
- We would rather say that plainly than imply a scale we do not have. It is also why the work is scoped in increments you can stop at.
- Why are there no case studies?
- Because we have not earned them yet, and inventing them is not an option we are willing to take. When there is work we are allowed to describe, it will appear with the client's name on it.
- In their place there are four worked examples on this site you can click through — real logic, synthetic data labelled as synthetic, and every rule on show. They are meant to be checked rather than admired.
- Where do you work?
- Remotely, with clients wherever they are. The company is based in Vadodara, Gujarat, and the staffing work is largely with firms outside India.
Something not answered here
Ask it directly — hello@twishivplatforms.com or the contact form. You will hear back from the person who would build it, within one business day.
Find one workflow worth automating
You do not need to replace your technology stack. Start with one process that costs your team hours every week.