Skip to content
Buildly
Draft pending legal review. This text summarises how the service is intended to work and may change before launch. The agreement you accept for your project is what applies.

Terms of service

Version 0.19-draft · Last updated

1. The service

Buildly provides Custom Software as a Service: we design and build software for your business and, for the duration of your subscription, host, maintain, and improve it. Each project is built to requirements agreed in a written scope.

We do not provide unlimited development or unlimited hosting, and we do not promise instant delivery. What is included in your subscription is defined by your plan and your accepted scope.

2. Plans, scope, and agreement

  • You select a plan, platform, and billing interval for running and submit a project brief. The plan sets the minimum build months and the running price.
  • We review the brief and prepare a versioned written scope in your customer portal describing deliverables, exclusions, timeline, build months, price, and when payments start. Scoping is free. If the work exceeds the selected plan, we propose a published plan that fits or a reduced scope.
  • A scope is a quotation valid for 14 days from the day we send it. You may comment on any part of it and ask for changes before you approve it. Approving the scope accepts the scope, the quote, and these terms.
  • Work and billing begin only after you approve the scope. Later edits to your brief do not change an accepted agreement.
  • Unless a published bundle applies, a project covers one agreed platform. Additional platforms, such as an app for your website, add build months to the project; they never carry a setup fee.

Delivery runs in the stages listed in your scope, which always starts with the scope and may include wireframes, design, build, and launch, depending on what the project needs. You review and approve each stage in your customer portal before we move to the next. Where included, wireframes and design each begin with three directions on your key screens; you choose one, which does not use a round of changes, and we complete the stage in that direction. Each stage includes 3 rounds of requested changes, and choosing a direction includes up to 10 rounds of its own. Each extra round costs $10 and is paid in your portal before work on it starts; you may request a call instead.

3. Build, running, and billing

Projects are paid in two phases. While we build your project, you pay the build rate of $100 a month, the same on every plan, for the number of build months set in your scope, which is never fewer than your plan’s minimum: Essential 1 month, Growth 3 months, and Business 6 months; Scale by agreement. There is no setup fee, and nothing is paid in advance. Your scope states when build payments start; unless it says otherwise, they start when you approve the scope.

Extra build months, at the same rate, are added only when you add to the agreed scope or the work waits on you, for example for feedback, content, or approvals. Each extra month is agreed with you in writing in your customer portal before it is invoiced. Delays caused by us never cost you an extra month.

When the build is complete, the build payments stop and running starts at your plan’s running price, which covers hosting, security updates, backups, and monitoring. Running is month to month, or yearly at 12 times the monthly price where the plan offers it: you may stop at any time.

Payments are made online through PayPal, our payment processor, in your customer portal. Build and running payments are taken automatically through PayPal on the same day each month (or year) as the first payment of each. Change requests and extra build months are invoiced on their own.

Your data belongs to you at all times. Until your plan’s minimum build months are paid, we export it on request in a convenient format suited to the data, but the source code is not handed over. Once they are paid, you own the agreed source code and the database, and may continue running the application with us at the running price or move it elsewhere. Cancellation takes effect at the end of the period you have already paid for; see the cancellation policy.

Launch prices: where a plan shows a launch running price next to its regular price, the launch price is the price you pay if you subscribe while it is offered, and you keep it for as long as your subscription continues without interruption. If you cancel and subscribe again later, the price shown at that time applies.

4. Changes after delivery

Fixes to delivered work that does not work as agreed are free. Every other change is a change request: we estimate it, and it is charged, on its own invoice, only if you approve the estimate. Plans do not include an allowance of change requests. Requests are handled one at a time.

5. Integrations, add-ons, and third-party costs

  • Standard integrations cost $20 each, one time, per approved integration, within the scope defined for that integration. They do not include unlimited workflows, data mapping, or future changes.
  • Migrations and complex enterprise integrations are priced by quotation.
  • Third-party accounts, services, licences, API and messaging usage, payment processing, and app-store charges are supplied and paid by you.
  • Hosting upgrades are separate add-ons and do not change your software plan.

6. Ownership and handover

The agreed source code and the database are delivered once your plan’s minimum build months are paid and required payments have been made. Handover includes the agreed code, build and deployment instructions, a dependency manifest, a schema and data export, configuration examples without secrets, architecture notes, and licence information. Handover does not automatically cancel hosting or maintenance. You do not acquire ownership of third-party software, which remains subject to its own licence.

7. Maintenance for existing software

Maintenance for software we did not build starts at $20/month after an assessment. We publish the supported scope before you accept, and any additional charge must be accepted by you before work starts.

8. Your responsibilities

  • Provide accurate requirements, content, and timely feedback and approvals.
  • Maintain the third-party accounts your software depends on.
  • Share credentials only through the secure method we provide, never in comments or messages.

9. Acceptable use

These rules apply to everything built or hosted on Buildly, including the websites, shops, and apps you build yourself with our AI or your own. You may not use Buildly to publish or send:

  • adult or sexual content, or content offering sexual services;
  • anything illegal, including the sale of illegal goods or services;
  • hate, harassment, or threats against anyone;
  • scams, phishing, malware, or anything meant to deceive or harm visitors or their devices;
  • content that pretends to be another person, business, or organisation;
  • content that infringes the rights of others, such as their copyright, trademarks, or privacy.

We check photos when they are added and content before it is published, partly with automated tools. We may review any site or app, refuse to publish content, hold a publish until our team has reviewed it, or suspend a site or app that breaks these rules, and we will tell you why. A suspended site or app stops showing to visitors and cannot be edited until we restore it.

To report a site or app that breaks these rules, email [email protected] or use the Report a site page.

10. Terms still being finalised

Liability, warranties, governing law, dispute resolution, and similar provisions will be added after legal review. Until then, the agreement you accept for your project governs.