> ## Documentation Index
> Fetch the complete documentation index at: https://docs.virusstudio.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Script Turnaround Time: When to Expect Your Delivery

> See how long Virus Studio takes to deliver scripts by complexity tier, and learn how to speed up your project with a clear, detailed request.

Knowing when your script will be ready helps you plan ahead. At Virus Studio, delivery timelines are driven by the complexity of your project — simpler requests move quickly through the queue, while larger systems naturally take more time to build and test properly. Here is what you can expect at each tier.

## Delivery Timelines by Tier

| Tier         | Typical Turnaround |
| ------------ | ------------------ |
| **Simple**   | 1–2 business days  |
| **Standard** | 2–4 business days  |
| **Complex**  | 4–7+ business days |

These estimates reflect normal queue conditions. If your project is unusually large or has special requirements, we will let you know during the quoting stage.

## Rush Delivery

Need your script sooner? Rush delivery is available for an additional fee. When you submit your request, mention your deadline and we will confirm whether rush turnaround is possible and what the adjusted cost would be. Rush slots are limited, so the sooner you reach out, the better.

<Note>
  Turnaround time starts only after all project details are confirmed — including your approval of the quote, any reference files you need to share, and answers to any clarifying questions we send your way.
</Note>

<Warning>
  Incomplete or vague requests can significantly delay your delivery. If we have to pause work to ask follow-up questions or wait for missing information, that time is not counted against your turnaround window. The more detail you provide upfront, the faster we can get to work.
</Warning>

## Tips for Faster Delivery

Following these steps helps us start immediately and avoid back-and-forth delays:

<Steps>
  <Step title="Write a clear description">
    Describe exactly what your script should do, including inputs, outputs, and any edge cases you already know about. Avoid vague language like "make it work better."
  </Step>

  <Step title="Share existing code">
    If your request builds on or modifies code you already have, include it in your submission. This removes guesswork and prevents us from duplicating work you've already done.
  </Step>

  <Step title="Respond promptly to follow-ups">
    If we send you a clarifying question, a quick reply keeps your project at the front of the queue. Delayed responses push your estimated delivery date back by the same amount.
  </Step>

  <Step title="Confirm the quote quickly">
    Work begins only after you confirm the quote. The sooner you approve, the sooner your project enters active development.
  </Step>
</Steps>

## Related Pages

<CardGroup cols={2}>
  <Card title="Pricing" icon="dollar-sign" href="/working-with-us/pricing">
    Understand how project complexity and urgency affect your quote.
  </Card>

  <Card title="Delivery" icon="box" href="/working-with-us/delivery">
    Learn what to expect when your finished script arrives and how to get it running.
  </Card>
</CardGroup>