Custom Services Terms

Enquiries and proposals

Sending an enquiry does not create a contract and does not oblige us to quote. We aim to respond to every enquiry. Information you send is treated as confidential and is used only to assess and respond to it.

A project begins with a written proposal — a statement of work naming the scope, the deliverables, the fee, the payment schedule and the assumptions it was priced on. Nothing on this website is a quote. Figures published as engagement ranges are there to help you plan and are not binding on either side.

Scope and change requests

The statement of work is the scope. Anything not named in it is out of scope, including work that seems small — a change of platform, an extra integration, a second language, a new user role. That is not a refusal: it is how a change gets priced honestly instead of absorbing time nobody planned for.

A change request is agreed in writing before it is built, with its own effect on the fee and the timeline stated at the same time.

What we need from you

Most delay on a custom project is waiting, not building. These are the things only you can supply:

• Content, copy, images, logos and brand assets, and the right to use them.
• Access to any existing system, account or data the project has to work with.
• One person who can make decisions and give approvals.
• Review and feedback within the time the statement of work allows for it.

Timelines assume these arrive when they are needed. Where they do not, the schedule moves by at least the length of the wait, and we will say so at the time rather than at the end.

Third-party costs

A project usually depends on services neither of us operates: hosting, domains, an email or SMS provider, a payment provider, an AI provider, a map or search service, an app store account. Those are billed by their own providers to you, on their own terms, and are not included in the project fee unless the statement of work says they are.

Wherever possible these accounts are opened in your name, so you keep control of them if we stop working together.

Fees and payment

The fee, the deposit, the payment schedule and what happens if an invoice is late are set in the statement of work for that project. We do not publish a standard figure for any of them, because a fixed deposit that suits a two-week prototype does not suit a six-month platform.

Where an invoice remains unpaid beyond the period the statement of work allows, we may pause work after telling you in writing. Pausing is not termination and the work already done is not deleted.

Delivery, acceptance and fixes

Deliverables are handed over against the statement of work. You get a review period, named there, to check them against what was agreed.

A defect is something that does not do what the statement of work says it does. We fix those. A change of mind about what it should do is a change request, priced as one. Whether a warranty period for defects is included, and how long it runs, is set in the statement of work.

Maintenance and support

Ongoing maintenance, monitoring and further development are a separate arrangement with their own fee. A project that ends without one still belongs to you and keeps running; it simply is not being watched by us.

Who owns what

Three different things are produced by a custom project and they are not owned the same way:

• Work made specifically for you — your custom code, designs and content. Assigned to you on the terms and at the point the statement of work states, which is normally final payment.
• Midcrowd's pre-existing components, tooling and know-how that we reuse to build it. These stay ours; you get a perpetual licence to use them as part of your deliverable, not ownership of the component itself.
• Open-source and third-party software. Owned by whoever owns it, and licensed to you on that licence's terms, not ours. We tell you what a deliverable depends on.

We may describe the work in general terms as a reference unless the statement of work says otherwise.

Credentials and confidentiality

Each side keeps the other's non-public information confidential. Where you give us access to a system, give the narrowest access that lets the work happen, and issue it to a named account we can hand back or you can revoke. Do not send passwords or keys by email or chat.

Where we process personal data on your behalf as part of the project, the Data Processing Terms apply.

Ending a project

Either side can end an engagement in writing. You pay for work completed and for commitments already made on your behalf up to that point; we hand over what has been produced and paid for, together with the access needed to keep using it.

Liability

Neither side is liable to the other for indirect or consequential loss. Our total liability for a project is limited to the fees paid for it, except where the law does not permit that limit. Nothing here excludes liability that cannot lawfully be excluded.

How to contact us

Questions about this document can be sent to midcrowd.ai@gmail.com. We aim to respond within 5 business days.

Midcrowd is the name this service trades under. The registered legal entity and address are to be confirmed before these terms are final.