Contact

Contact CodaRoq

Tell us what keeps repeating.

A useful first message does not need a polished specification. Describe the current task, how often it happens and what a better result would look like.

Direct contact

Start by email.

CodaRoq currently uses direct email rather than a public form. This keeps the first contact simple and avoids adding another data-processing service before it is needed.

Email CodaRoqinfo@roellin-racing-shop.chOpen an email →
OperatorRöllin Racing GmbH
AddressKnonauerstrasse 52b, 6330 Cham, Switzerland
LanguageEnglish or German
Websitecodaroq.com
Project brief

Five points are enough.

Copy these questions into the message and answer them in plain language.

01What is the task?Describe the current sequence from start to finish.
02How often does it happen?Per day, week or month — and roughly how long it takes.
03Who is involved?Roles, permissions and handovers between people.
04What data enters and leaves?Products, fields, files, emails, reports or external systems.
05What would a good result be?The outcome, not just the feature you imagine.
Copyable outlineCurrent workflow: Frequency and effort: People and roles: Inputs and outputs: Desired result: Important exceptions:
Before sending

Please do not include passwords, API keys, access tokens, confidential customer records or unnecessary personal data. Examples can be anonymised. More detail can be exchanged later through an agreed secure method.

What happens next

A practical first review.

The first response aims to clarify fit and the unknowns. It is not an automatic promise that every idea should become a custom plugin.

01 / FIT

Check the workflow

Is the task frequent, definable and important enough to justify custom development?

02 / QUESTIONS

Identify the unknowns

Which systems, edge cases, permissions and dependencies need to be understood?

03 / NEXT STEP

Choose a sensible route

A scoped proposal, a smaller discovery step, an existing tool — or an honest recommendation not to build.