Questions before you get started.
The proposed service is explicit about systems, access, costs, staff involvement, exceptions, ownership and service status.
How do I get in touch?
Email hello@threadworksai.com for general enquiries or bill@threadworksai.com to contact Bill directly. These links open your email app. This site has no contact form or booking flow.
What kinds of systems can be included?
We check the available APIs or connectors, licenses and permissions for the exact workflow. A connection must be tested in an authorized customer environment before it is promised. If a live connection is unsuitable, an initial project can use approved exports or a manual handoff.
How is access handled?
The setup plan defines the accounts, approved records and actions the job needs. Client separation, authentication, provider data handling and approval checks must be verified before live use. See our security and access approach.
How are costs discussed?
Costs should be separated into implementation or setup work, ongoing management, and any provider or usage charges. Support scope, new work and response expectations also need to be agreed. Pricing is agreed for the specific scope before work begins.
What do staff do after implementation?
Intended users practice the actual task: inspecting sources, correcting an output and routing an exception. Review and business accountability remain with the people who own the work.
What happens when information is missing?
The workflow should surface the gap and route it to a named exception owner. It should not invent a fact, promise an outcome or quietly complete a record that needs human judgement.
Who owns the workflow and what if the service ends?
The business keeps control of its records, decisions and approvals. The written scope defines ownership and usage rights for outputs, configured workflows, reusable components and third-party software. Offboarding covers agreed exports and documentation, access removal and retention arrangements.
How long does implementation take?
Timelines depend on scope, current process, source quality, access, required testing and staff availability. A narrow first workflow is generally easier to validate than a broad multi-system change; we agree on a realistic schedule after reviewing the task.
Do the demos connect to real business systems?
No. The website demos use fictional, prewritten examples in your browser. They do not run live AI, send messages or connect to customer systems. A client implementation requires separately agreed access, testing and approval.