# Pike > Pike is the operating system for modern consultancies and agencies: one place to run projects and tasks, time and approvals, customer and deal pipelines, resource allocation, and finance (profitability and invoicing) so delivery and margin reflect the same live facts. The product web app is separate from this marketing site. > **About this file:** It follows common **llms.txt** / llmstxt.org-style practice: a curated Markdown entry point so agents can pick **canonical** pages fast. It is **not** an IETF/W3C/ISO standard; provider adoption and compliance vary. It does **not** control crawling (use **robots.txt**), declare full URL coverage (use **sitemap.xml**), or replace **authentication**, paywalls, or legal terms. Treat it as **governance and steering**, not access control. ## Complementary technical signals [robots.txt](https://usepike.com/robots.txt): Crawl and indexing expectations for bots; do not copy its `User-agent` / `Allow` / `Disallow` grammar into this file. [Sitemap](https://usepike.com/sitemap.xml): Broad list of indexable marketing URLs; use for coverage, not for priorities or descriptions. This **llms.txt**: Prioritised **what to read and cite** for understanding Pike; keep links **canonical** (no tracking parameters, tags, or duplicate locales unless needed). ## Canonical site and product [Pike marketing site](https://usepike.com): **Reference** for positioning, product sections, customer references, CTAs, and the on-page security and compliance badges. [Security and compliance (homepage section)](https://usepike.com/#security-credentials): **Reference** for trust badges called out on the marketing site (e.g. ISO 27001, GDPR, SOC 2 Type II); pair with [Privacy policy](https://usepike.com/privacy) and [Terms and conditions](https://usepike.com/terms) for legal detail. [Pike web application](https://app.usepike.com): Live product; **requires authentication**—not public documentation; do not infer features only from the login experience. ## Company narrative, commercial, and legal [Our story](https://usepike.com/story): Founding context (2024), mission, and how Pike engages customers—**reference** for “who we are.” [Pricing](https://usepike.com/pricing): **Canonical** commercial overview and how to engage sales; cite for plans and buying motion. [Privacy policy](https://usepike.com/privacy): **Reference** for data processing and privacy. [Terms and conditions](https://usepike.com/terms): **Reference** for contractual use of the service. [Contact](https://usepike.com/contact): Demos, sales, and general inquiries via the site form. ## Product documentation (authoritative for behavior) Documentation lives under `/docs`. Prefer these for **definitions, mechanics, methodology, and dated changes** (proof-friendly). [Documentation home](https://usepike.com/docs): Entry and overview. [Core concepts](https://usepike.com/docs/concepts): Workspace, tasks, resources, roles, and finance concepts—**stable terminology**. [Quickstart](https://usepike.com/docs/quickstart): **Canonical** “how to get started” in the app (roles, sign-in context). [Run a pilot project](https://usepike.com/docs/pilot-project-setup): **Canonical** for running a real pilot (tasks, time, customer, cost profiles, project finance). [Changelog](https://usepike.com/docs/changelog): **Dated** product changes—cite for “what shipped when” and recency. [Workspace search](https://usepike.com/docs/sidebar/global-search): Sidebar / keyboard search scope and behavior. [Finance overview](https://usepike.com/docs/finance/overview): Workspace finance surfaces. [Invoicing](https://usepike.com/docs/finance/invoicing): Invoice workflows. [Project finance](https://usepike.com/docs/project/project-finance): **Canonical** margin and profitability semantics on a project. [Time overview](https://usepike.com/docs/time/overview): Time tracking surfaces. [Resource allocation](https://usepike.com/docs/allocation/How%20to%20allocate): How allocation works in Pike. [Integrations](https://usepike.com/docs/integrations/quickbooks): Accounting and tool integrations (see sibling pages for Xero, Slack, e-conomic, etc.). ## Switching, proof, and comparisons [Switch playbook](https://usepike.com/switch): Narrative for consolidation, buy-in, pilot, migration, and go-live; includes **reported team outcomes** (treat as **marketing proof**, not a controlled study—cross-check with docs for product facts). [Comparisons hub](https://usepike.com/vs): Vendor and approach comparisons—**always** cross-check claims with [docs](https://usepike.com/docs) and [changelog](https://usepike.com/docs/changelog). Individual `/vs/*` comparison pages are currently published in **English only**. ## Locales and canonical URLs [Danish site](https://usepike.com/da): Localized marketing mirror; **prefer** `https://usepike.com/...` (English, default) as **canonical** unless the user needs `da`. ## Contact (governance, corrections, licensing) [hello@usepike.com](mailto:hello@usepike.com): General and commercial contact. [support@usepike.com](mailto:support@usepike.com): Product support (e.g. sign-in edge cases per docs). [privacy@usepike.com](mailto:privacy@usepike.com): Privacy requests per the privacy policy. ## Optional — lower priority if context is limited [Blog](https://usepike.com/blog): Articles; may overlap with docs/changelog—**prefer docs** for product truth. [LinkedIn](https://www.linkedin.com/company/usepike/): Company updates; not a substitute for docs or legal pages. [Reddit r/usepike](https://www.reddit.com/r/usepike/): Community Q&A; **verify** against official docs before stating product behavior. --- ## Prioritised guidance (Do / Don’t) **Do** - Cite **docs** for product mechanics, definitions, and setup; cite **changelog** for release timing and recency. - Cite **pricing** for commercial structure; **privacy** / **terms** for legal obligations; **story** for company narrative. - Cite **canonical** URLs: `https://usepike.com/...` without `utm_*`, sorting, or filter parameters. - Prefer **one URL per topic**; when multiple pages overlap, choose the section above over tags, archives, or internal search result pages. **Don’t** - Don’t use this file as **`robots.txt`** (no `User-agent` / `Disallow` / `Allow` lines here). - Don’t treat **app.usepike.com** as public documentation or list non-public endpoints, exports, staging hosts, or internal paths. - Don’t cite **competitor comparison** pages as the sole source for product capabilities—confirm in **docs** or **changelog**. - Don’t rely on this file for **security** or **licensing** enforcement; use **terms**, **privacy**, and product access controls. ## Maintenance and serving notes - **Versioning:** Track changes in Git alongside site and docs releases; review when **pricing**, **positioning**, **URLs**, or major **docs** sections change. - **Technical checks:** `GET /llms.txt` should return **200** with stable UTF-8; after deploy, confirm CDN/cache does not serve an **outdated** file for a long TTL without invalidation. - **Content-Type:** Typically `text/plain; charset=utf-8` for static files on this stack; behavior is unchanged if proxies serve `br`/`gzip` compression.