> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/billing-policy-time-based-work.md). # Billing Policy: Time-based work All consultancy, custom development, and similar project work is billed on a **time-and-materials basis** — you pay for the hours actually spent, not a fixed quote. ### Work estimated under 10 hours Any task estimated to take **less than 10 hours** is automatically approved and started without a separate approval step. We don't run a formal estimation process for small tasks. Producing a reliable estimate takes real time — often nearly as long as the task itself — so for work under this threshold, we skip that step and just get started. ### Why we work this way * **Estimating is not free.** A careful estimate for a small task can take almost as long as doing the task. Requiring estimates on every small item would roughly double the total time (and cost) spent on it. * **Small tasks carry small risk.** At under 10 hours, the downside of proceeding without a pre-approved estimate is limited, so we default to moving fast 🚀 * **You're billed for actual time**, always — not for a guess. If a task runs longer than expected, you'll see that reflected in the time reported, not in a surprise change order. ### What this means for you * Tasks under 10 hours: work starts immediately, billed by actual time spent 🚀 * Tasks estimated at 10 hours or more: an estimate is prepared and shared for approval before work begins 🤝 If you'd like an estimate on a smaller task anyway, just ask — we're happy to provide one, with the estimation time itself billed as part of the work. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.flowretail.com/docs/billing-policy-time-based-work.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.