Working with us

Engagement kickoff with ForePath

Purpose of kickoff Kickoff aligns scope, contacts, access, and communication so delivery can start without guesswork. It usually follows an accepted proposal or signed statement of work. Typical kickoff agenda 1. Confirm scope, milestones, and acceptance criteria from the proposal or SOW. 2. Name primary contacts on both sides (technical, commercial, escalation). 3. Agree channels. Portal updates, live chat during business hours when the widget is available (cookie consent required), and [email protected] for async mail. 4. List access required for delivery, with a safe credential handover method. 5. Set the first delivery checkpoint and how status will appear in the portal. What we need from you - A named decision maker for scope changes - Technical contacts who can grant or revoke access - Billing and invoice recipients, including VAT ID where required - Any constraints (change windows, data residency, security review gates) Hours and response aims Support business hours are Monday to Friday, 09:00 to 17:00 Europe/Berlin, excluding public holidays in North Rhine-Westphalia, unless your contract says otherwise. Published response aims (not contractual SLAs) for general Support are about two business days. Contract SLAs override Help defaults.

Roles and what we need from you

Typical roles Exact titles vary by organization. Common roles include: - Commercial contact. Approves proposals, change requests, and billing details. - Technical contact. Provides systems access, reviews technical deliverables, and joins acceptance. - Security or compliance contact. Reviews security questionnaires, access policies, and data handling. - Day-to-day requester. Opens routine Support requests and follows delivery updates in the portal. What keeps work moving We usually need timely answers on: - Scope clarifications and priority when multiple workstreams compete - Access grants and revocations when environments change - Acceptance of milestones (approve, reject with reasons, or request a rework path) - Invoice and VAT data that match your legal entity What not to send in general chat or hi@ Do not paste production passwords, private keys, OTP codes, JWTs, API keys, full database dumps, or vulnerability exploit details into general Support chat or [email protected]. Use the secure handover path agreed at kickoff. Use [email protected] for vulnerability reports, and the privacy path in Security & privacy for data-subject requests.