Send us what you need done
Put the work on our desk.
You do not need to choose the right service or prepare a polished brief. Tell us what needs finishing, fixing, researching, analysing or systemising; attach the file or public link if useful. We will scope the smallest useful finished result.
Simple by design.
Send what you have
Confirm scope / price
Pay securely
Receive the result
No discovery call or polished brief is required. Do not send passwords, card details, login credentials or highly sensitive account information.
Choose the outcome — or let us route it
Start with the problem, not a consulting category.
Clear jobs go straight to a fixed scope. Ambiguous or boundary-crossing work is routed for review before payment.
R990 · SPREADSHEET
Fix a workbook or CSV
Clean, repair and simplify one supplied spreadsheet.
R1,990 · DECISION
Compare and decide
Turn supplied context and evidence into a recommendation.
R1,990 · AUTOMATION
Package a repeated process
Get workflow logic, prompts, controls, tests and handover.
R1,490 · DOCUMENT
Finish an existing document
Use the dedicated Document Finish production workflow.
NOT SURE
Describe the mess
Our routing engine will choose the smallest safe next step.
Written brief
Start with what you already have.
No polished brief required. A sentence, file, spreadsheet or public link is enough to begin.
Project received
Your private project page is ready.
Reference:
If the request fits a fixed-scope service, your private page shows the scope, price and secure checkout immediately. Boundary-crossing work is held for review before any payment request is issued.
Service information
Privacy & Data Handling
This section describes what the current T Bruce Studio forms collect and how their service workflows handle submissions, based on the published application behaviour.
Information you may submit
Depending on the form, this can include your name and email, organisation or business details, a project brief, a public website address, timing information, technical context, document text and optional uploaded files. Only provide information needed to scope or complete the request.
How submissions are handled
- Project enquiries are saved to a private T Bruce Studio record. If you attach files, the application uploads them to associated file storage. A new enquiry may also trigger an email notification to the studio inbox.
- The free website scan reads the public URL you submit and uses the stated business and visitor goal to prepare a short review. The resulting preview is stored so a recent scan can be reopened; the application uses the email and website address to limit duplicate scans.
- Document Finish stores the document text, purpose and contact details with the order record. When a paid order enters production, the submitted text is sent through the configured AI production and quality-check workflow; the finished file and delivery status are stored for delivery.
- Spreadsheet Rescue stores the uploaded XLSX or CSV with the project record. Before payment, the application checks whether the file is within the safe automated-repair boundary. After verified payment, simple spreadsheets are processed deterministically, the repaired workbook is reopened for validation, and the finished XLSX is stored for secure delivery. Complex or unsafe-to-rewrite workbooks are held for exception review rather than automatically altered.
- Business and MoleculeX service forms save the submitted brief or technical details to the relevant project or order record so the request can be assessed and managed.
Service providers used by these workflows
The application stores records and uploads through its AppDeploy database and file-storage services. Project enquiry alerts are sent through Resend when that email integration is configured. Website scans and paid Document Finish orders use the application's configured AI processing; the underlying model and provider-side retention are not visible in the application code. Where checkout is offered, payment takes place through the existing Yoco checkout flow; the forms on this site do not ask you to enter card details.
The application code shows these service calls, but it does not establish the providers' own retention periods or every infrastructure-level handling practice.
Retention and deletion
The current application behaviour does not establish a fixed retention period or complete deletion process. No specific retention promise is made here. Provider-side retention and backup behaviour also require confirmation before they can be described.
Questions about information you submitted
Use the project form above and identify your message as a privacy or data question. Please include only the details needed to locate the submission. Do not attach documents or include passwords, payment details or other sensitive information in a privacy request.
This section describes observed form and application behaviour; it does not claim legal certification, independent review or compliance status.