Teloa operates on a structured capacity model. This section applies to requests made under a subscription plan, where each request represents a reasonable, focused scope of work. We advise keeping a single plan request to one clear deliverable. It moves faster that way, and the timeline is easier to hold.

Custom projects work differently. There is no single-deliverable guidance and no fixed catalog to choose from: tell us what you want built, at whatever size or shape it takes, and we scope, quote, and plan it around your project.

Examples of a focused plan request:

• One landing page
• One dashboard flow
• One logo concept direction
• One ad designs set (within defined limits)
• One no-code page build (Framer or Webflow)

Where a plan request bundles several large deliverables, we will usually suggest splitting it so each piece gets its own timeline, or handling it as a custom project instead.

When you submit a request, you propose your preferred timeline. Teloa approves it, or reviews it with you, before work starts. Approval is based on a standard scope assumption:

• A clearly defined brief
• A focused outcome
• A reasonable quantity for that service type

Once a timeline is agreed, work proceeds on that commitment, and deliverables start landing within the first 48 hours.

If a submitted brief exceeds what is a reasonable single deliverable for the selected service:

• The request is reviewed by the Teloa team
• You will be asked to split the work into multiple requests, or Teloa will split it with your confirmation
• Each split request follows its own timeline and uses its own active slot
• If the work is better handled as one continuous project, Teloa may instead propose it as a Custom Development & Projects request, scoped and quoted as a whole

In short: if the scope exceeds a reasonable single deliverable, it becomes multiple requests or a quoted custom project.

This ensures:

• Predictable timelines
• Fair capacity allocation
• Consistent service quality
• No mid-project disruptions

• Minor adjustments are handled as revisions, and we keep revising until you're satisfied
• Significant changes or new requirements may be treated as a new request
• If a change substantially alters the agreed scope, the Teloa team will flag it and confirm the path with you before continuing

Work that doesn't fit the standard catalog can be raised as a custom request:

• Describe what you need designed or built
• Teloa scopes it and sends a fixed quote before any work starts
• Payment is made once you approve the quote and timeline
• Custom requests follow their own agreed timeline

Existing Teloa users: everything happens in the app, on the request itself. Scoping, quoting, payment, delivery, and completion all run through that request's thread, so the full history stays in one place.

New users coming from the landing page: submitting the form raises a request automatically, and it arrives in the app as your brief. Once we have scoped and quoted it, you're invited to Teloa by link to review everything in one place. From that point the process is identical to an existing user's: review the quote and project plan, approve it, pay, and follow the work through delivery and completion in the app.