Patch · v25
The short answers, then the longer ones.
Delivery · Short answers from the catalog, grouped by topic.
The questions below come from the catalog: how a month is calculated, what happens to unused time, which form to use, and who receives the email. Under them is the reasoning those answers leave out.
If your question is really “what should we buy”, there is nothing to buy on this site. Pick the form that matches the conversation. If your question is “which line”, start with the guide on choosing an engagement, then write to us with the job in a paragraph.
Public pages · review before you write
No questions match that search. Try another word, or Send a note to engineers below.
Core · v3
Pricing
A monthly engagement is the hourly rate times 30. Project work stays at the hourly rate.
Yes. Type any count from 1 to 40,000. The total is that count times the country rate. A bundle only fills the count in for you.
Prepaid hours stay on the block until they are used. Monthly blocks are a fresh allocation and do not roll over.
No. Requesting hours saves the block and emails both sides. Work starts after the scope is confirmed. A card is not taken on this site.
Engagements
A pilot proves one job on your material and ends with a continue, narrow, or stop decision. An agent build is the larger block for a defined queue, still with a person in the loop.
Integrations and automations join the tools you already pay for. A new application is a software engagement, scoped separately.
Someone on your side. The draft can cite a source. It does not leave the building until a person sends it.
Contact
No. Fill in the contact form. We store it and email a confirmation to the address you entered.
Start a project if you know the job. Request a quote if you want a starting engagement priced. Book a conversation if you would rather talk first.
The confirmation goes to the email address on the form. The same details also go to the studio inbox, so a reply can come back to you.
Yes. The note is stored, a copy goes to the studio inbox, and a confirmation goes to the address you typed. The page tells you if either send failed.
Enquiries and hour requests are delivered to the studio inbox configured on the API, and the confirmation is sent to the customer with that inbox as the reply address.
The reasoning under the short answers
A calendar month hides the arithmetic. Thirty is the multiplier we publish, so a ₹200 hour is ₹6,000 for the month on every page that shows a monthly line. February does not make the care cheaper.
A rollover becomes a balance nobody can explain. The month is a fresh allocation for a queue. If you needed a bank of hours for a defined job, that job should have been a fixed block.
The conversation is email. An account would imply a dashboard of orders. This site stores the enquiry and sends a confirmation to the address you typed. Reply continues in the mail.
The page tells you when the mail provider refused the send. The enquiry is still stored. Write again from the same address, or wait for the studio reply to the address you entered. Check the spam folder before you assume it failed silently.