Contact
Bring one process. Get a real answer.
No forms, no gatekeeping, no discovery call with a sales engineer who cannot build. Write to us with one process and its rough volume, and you will get a straight response — including “this is not worth automating”.
info@helixworks.site
Best for process descriptions, volumes and sample documents. The reply comes from an engineer.
Phone
+1 (650) 442-5844
Mon–Fri · 9:00–18:00 PT · Pacific Time (UTC−8). A person answers; there is no phone tree.
Studio
One Ferry Building, Suite 210, San Francisco, CA 94111
Visits by appointment. We also work on site with client teams for discovery weeks.
What to send
Four lines beat a long brief.
You do not need a specification to start. These four things are enough for us to tell you whether it is worth automating and what a pilot would look like.
Response time
One business day — and the reply comes from an engineer, not a sales sequence
We sign a mutual NDA before looking at anything sensitive. Send the NDA first if your process requires it — we will sign and return it the same day.
- 01
The process you want off your team’s plate, and roughly how many items per month
- 02
Which systems are involved, and whether they have APIs
- 03
Who does the work today, and what breaks most often
- 04
What “better” means for you: hours saved, error rate, days-to-close, response time
First call, in practice
- 1 You describe the process and where it breaks.
- 2 We ask about volumes, systems and who signs off on changes.
- 3 We sketch how we would automate it — and what we would not automate.
- 4 You get a written note afterwards: options, effort and a price for discovery.
How quickly can we see something working?
Pilot in two to four weeks from kickoff, including discovery and blueprint. That assumes we get read access to a sandbox and a sample of real documents or tickets in the first week — that sample is the usual cause of delay.
What does it cost?
Discovery is a fixed fee, the pilot is a fixed price, and production is a monthly retainer with a defined scope. We quote after discovery because the honest number depends on your process, not on a price list. If a process is not worth automating, we say so and charge only for discovery.
Do we need to replace our systems?
No. We integrate with what you run — ERP, CRM, ticketing, data warehouse, and the legacy application with no API. Replacing your core systems is a different project and usually a worse idea than automating around them.
Next step
One process. Forty-five minutes.
Write when it suits you — we will come back with questions, not a brochure.
One business day — and the reply comes from an engineer, not a sales sequence