What we look at
An engineer, not a form-filler, reads what you send. For a website or store, we read your pages, your product catalog and your policies as a visitor would, and we look at what your platform exposes through its API: order status, tracking, stock, returns. For a support task, we look at the kinds of messages your task involves and which have an answer already written somewhere on your site. For an internal process, we look at the systems you named and what their APIs allow.
Then we apply the same four questions we use on every job. How often does the task happen? How long does each one take? What does an error cost? And does the data the automation needs exist somewhere it can reach, with an exception rate low enough that most cases run themselves? The method is written out on our page on choosing what to automate first, if you want to run it before you send.
What the one-page plan contains
One page, written in plain English, with five parts:
- What it would do. The assistant or automation described step by step, from the event that starts it to the result, including what it hands to a person and when.
- What it needs. The content it would answer from, the systems it would connect to, and whether your platform exposes the data. If something is missing (a policy that is not written down, an API that does not expose stock), the plan says what has to exist first.
- What it costs to run. Model fees and hosting estimated for the volume you gave us, billed by the providers to your own accounts. For most assistants, $40 to $200 a month.
- The fixed price to build it, with what is included: setup, connections, the test list, logs, 30 days of tuning. Or, if the honest answer is a tool, the name of the tool and roughly what it costs.
- The first ten test cases. Real questions or records the system would have to handle correctly before launch, so you can see at once whether we have understood the task.
The two working day promise
You get the plan within two US business days of your request arriving. Our engineers work India hours, so a request sent on a Monday morning in New York is usually answered by Wednesday morning. If a task needs more time to assess, we say so inside the two days and give you a date.
Sometimes the answer is "use tool X"
A fit check that ends in "do not hire us" is a good fit check. Some tasks are covered by features already inside your store platform, your helpdesk or your accounting software. Some are two-step connections you can set up in an hour in a tool like Zapier. Some are too small: we do not take jobs under $2,500, because scoping and testing would cost more than the work, and the result would be fragile. In each of those cases the plan names the tool or the setting, and we leave it there.
Good first tasks
The requests that most often turn into a plan with a price:
- Answering the same questions on your site: shipping, returns, fit, compatibility, hours. An assistant trained on your own content, from $3,500.
- Order status and return emails: hundreds a month, each needing a lookup. Support automation, from $4,500.
- Routing and qualifying enquiries from your site or marketplace into your CRM.
- Writing product descriptions from supplier spreadsheets in your house style, for a person to approve.
- Chasing suppliers for confirmation dates and recording the replies.
- Matching invoices to purchase orders and flagging the mismatches.
- The Monday report, pulled from four systems and written up before the meeting.
Each of those happens often, takes real minutes each time, has a clear rule, and lives in systems we can reach. That is the profile we are looking for. Workflow automation covers the internal ones, from $3,500.
Send the request
Use the form on this page, or email info@riantsoft.com with your site address and one sentence about the task. Either way, an engineer replies with the plan within two working days.