Frequently asked questions

You confirm the brief and authorise sharing its project materials with invited professionals. Borage structures the work, resolves needed inputs and seeks a suitable proposal. Submission alone starts no paid work or contract.

Review the final offer’s scope, total price, stages, date and corrections. You confirm that agreement before continuing to payment. When payments are enabled, the project starts after the required first-stage payment is confirmed. Registration does not commit you to a project.

Follow the exact payment plan in your offer. A staged project is funded one stage at a time before that stage begins. A smaller single-delivery project may use one payment. The professional cannot start an unfunded stage.

Use the review action to send one clear, consolidated request within the correction allowance in your saved agreement. That agreement determines whether the allowance applies across the contract or particular stages. A new direction or extra deliverable needs a separate agreement to scope, price and timing. If the allowance is exhausted or the parties disagree about what was promised, use the issue or project-desk action so a person can assess the evidence and next step.

No. AI notes help compare submitted work with the agreement. AI may return a bounded, observable missing requirement for correction before buyer review. You review the actual files and record acceptance, an included correction or an unresolved issue. Subjective quality and final acceptance remain your decision. If an AI note looks wrong, point to the relevant file and requirement through the review or project-desk action. Silence is not automatic acceptance in this POC.

No. Registration creates or opens your workspace and includes the platform terms confirmation at first email verification. You then review and approve a brief, review the final proposal and explicitly agree the project before payment. When payments are enabled, the project starts only after the required first-stage funding is confirmed. You can inspect public Terms, Project Terms and Privacy pages before making those decisions.

The payment flow checks Stripe’s signed confirmation against the expected order and relevant transaction details, including amount and currency. Funding is a prerequisite for the affected stage, and a recorded hold can pause its progress or release. Returning from Checkout does not by itself prove that work has started. If the workspace reports a pending or unresolved payment, check its status and contact the desk before paying again. No system can guarantee prevention of every payment problem or fraud attempt.

No. You can register, complete your profile and review invitations first. The workspace explains when Stripe setup is needed for a payable offer. The exact setup gate follows the current project flow.

Read the proposal, then use Confirm proposal to agree to its exact terms and confirm availability. You can ask a question, propose a change or decline using the reply form. Confirmation is conditional on selection and the buyer’s acceptance; do not begin work until your workspace opens the funded stage.

Accepted stage payments are normally scheduled 48 hours after buyer acceptance, subject to the saved terms, Stripe readiness, currency and release checks. A recorded hold can pause the affected transfer while an issue is reviewed. Payment sent means Stripe accepted the Connect transfer; bank arrival may take longer. Completing the contract and receiving a bank payout are different events. If payment status is unclear, contact the desk with the project reference.

Ask a question or propose a change before using Confirm proposal. Identify the missing input or unclear requirement and the effect on price, delivery or responsibilities. Confirmation means agreeing to the specific proposal and your availability; it remains conditional on selection, buyer acceptance and required funding. Once work is active, report a material obstacle promptly. A missing input does not automatically change a deadline or authorise extra work.

Read the written project terms. The POC’s default is a non-exclusive licence for the buyer’s intended project use after acceptance and full payment; ownership transfer or exclusivity needs an explicit written term. Third-party fonts, stock assets and tools retain their licences. Do not assume you may publish a client’s confidential materials or display the project in a portfolio without permission. Raise ownership, licence restrictions and portfolio expectations before confirming the proposal.

Your workspace keeps the agreed scope, payment plan, stages and history together. The completion record contains the frozen agreement and exact accepted files. Terms and Project Terms are also available as separate public pages.

Raise the issue from your contract or contact the project desk with the affected stage, agreed requirement, relevant evidence and desired resolution. A person can review the records and the supported next step; an affected workflow or release may be held while the issue is investigated. The proposed resolution should explain accepted work, remaining obligations and financial consequences. A request does not automatically refund a charge or undo a transfer. Applicable statutory rights and independent complaint routes remain available.

Authorised project participants, invited professionals within the sharing boundary you approved, administrators and configured providers needed to operate the workflow. For example, relevant text and files may be processed by an AI provider, and email providers receive information needed to send a notification. Read the Privacy Notice before supplying confidential or personal information. Ask the desk before uploading material with special confidentiality, sensitive-data or geographic restrictions.

Stripe sandbox payments use test cards and move no real money. A fictional test project is not a commercial order. Live payments remain unavailable until the separate launch checks are approved.

People make the important commitments: the buyer approves the brief, final agreement and delivered work, and the professional agrees their proposal and availability. AI helps with structuring, matching, routing, reply interpretation and delivery checks. Some ranking and selection can run automatically within configured rules; an administrator does not personally approve every routine step. Administrators handle exceptions and can pause affected activity. You can raise a concern with the project desk using the project record and evidence.

US participation is possible where the service, project type and payment-provider arrangements are available and lawful. Borage’s UK location does not by itself exclude US users. The draft chooses England and Wales law while preserving mandatory US federal and state rights, including applicable consumer and privacy protections. It is not certification of a launch in every state. The operator details, actual business model and relevant requirements still need review before live commercial use.

The workspace restricts access by role, project and task-link scope. Email sign-in links expire and work once, and sessions can be revoked by signing out. Relevant submissions have checks intended to reject requests from unrelated sites. Private task pages ask the browser to limit caching and referral of private links. Keep your email secure and do not forward private access, offer or review links. Report unexpected access to the desk. These controls reduce risk; they cannot guarantee that an incident will never happen.

No guarantee is given. The upload flow has supported-type and size limits, but those checks do not mean every file has been scanned for malware or cleared for intellectual-property rights. Upload only material you may share and use sensible precautions before opening files. Report a suspicious file or an unexpected request for credentials to the project desk. Do not put passwords, full card details or bank credentials into project text or files.

Use the available review, issue or project-desk action, or email projects@support.useborage.com. Identify the project, affected requirement or file, what appears wrong and the outcome you want. A person can review the evidence and supported next step. The desk can pause affected workflow steps or releases while an issue is investigated. It cannot invent buyer acceptance or silently change the agreed scope and price. Keep access links and credentials private; no immediate response time is promised in this POC.

Email projects@support.useborage.com with the information or project involved and your request. Depending on applicable law, you may have access, correction, deletion, copy, objection, restriction or opt-out rights, and some US states provide appeal rights. Proportionate identity checks and lawful exceptions may apply. Do not include passwords or complete payment credentials. The Privacy Notice explains the draft arrangements and the processes that still need completion before a commercial launch.