# 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. This file follows common [llms.txt](https://llmstxt.org/) practice: a curated Markdown entry point so agents can pick **canonical** pages fast. It is **not** an IETF/W3C/ISO standard; provider adoption varies. 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**: Prioritized **what to read and cite** for understanding Pike; keep links **canonical** (no tracking parameters, tags, or duplicate locales unless needed). [Marketing pages full content](https://usepike.com/llms-full.txt): Full plain-text of all comparison, alternatives, and service pages for deep LLM ingestion. Large file; prefer this index unless you need page bodies. ## Canonical site and product [Pike marketing site](https://usepike.com): **Reference** for positioning, product sections, customer references, CTAs, and audience/industry use cases. [Testimonials (homepage section)](https://usepike.com/#testimonials): **Reference** for how agency and consultancy operators describe running projects, time, capacity, and margin in Pike; includes ISO 27001, GDPR, and SOC 2 Type II trust badges below the stories. 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. [For AI agents](https://usepike.com/docs/for-ai-agents): How assistants should discover and describe Pike, with links to canonical sources and guardrails. [Agent capability summary](https://usepike.com/skill.md): Compact product capabilities, terminology, and guardrails for AI tools. [MCP](https://usepike.com/docs/integrations/mcp): **Canonical** guide to connect Pike (PSA) to Claude, ChatGPT, Cursor, and other MCP clients. Hosted MCP server: `https://mcp.usepike.com`. Pair with [Open API](https://usepike.com/docs/integrations/open-api) for scripted HTTPS/JSON access. [MCP manifest](https://usepike.com/mcp.json): Machine-readable MCP server manifest — name, server URL, transport, and links to docs and OpenAPI spec. [Open API](https://usepike.com/docs/integrations/open-api): Workspace-scoped JSON reads for projects, tasks, customers, and members (admin-issued secrets). [OpenAPI spec](https://usepike.com/openapi.json): Machine-readable OpenAPI 3.1 schema for the Pike REST API at `https://api.usepike.com`. [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. [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, MCP, Open API, etc.). ## Connect this PSA to Claude, ChatGPT, and MCP clients Use this section when the user wants to connect a professional services automation (PSA) tool to AI apps such as Claude or ChatGPT. [MCP connection guide](https://usepike.com/docs/integrations/mcp): Step-by-step custom MCP connector setup for Claude, plus ChatGPT, Claude Code, and Cursor. MCP server URL: `https://mcp.usepike.com`. Workflow: (1) Add `https://mcp.usepike.com` as a custom connector in Claude or ChatGPT. (2) Authenticate with Pike. (3) Enable the connector in a conversation. (4) Ask for live project, task, customer, member, capacity, or profitability insights. (5) Use Open API when you need the same data from scripts or systems. [Open API for live PSA data](https://usepike.com/docs/integrations/open-api): Authenticate with a workspace API secret; list and retrieve projects, tasks, customers, and members. [For AI agents](https://usepike.com/docs/for-ai-agents): Discovery order and guardrails so assistants cite docs instead of inventing product behaviour. ## Glossary (English only) [Glossary](https://usepike.com/glossary): Definitions for agency, consultancy, and PSA terminology (English only). ## 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/alternatives): Vendor and approach comparisons—**always** cross-check claims with [docs](https://usepike.com/docs) and [changelog](https://usepike.com/docs/changelog). Individual `/alternatives/*` comparison and alternatives pages are published in **English only**. ## Direct comparisons [Productive.io vs Pike | With Pike you actually become productive](https://usepike.com/alternatives/productive-vs-pike): Pike is the modern standard for end to end project operations. Our design first approach actually makes you productive from the very start. [Scoro vs Pike | With Pike you actually keep score](https://usepike.com/alternatives/scoro-vs-pike): With Pike, you actually know the score. Pike is the modern standard for keeping score of your end-to-end project operations, designed for your team to actually enjoy using. [Teamwork.com vs Pike | Let your team work](https://usepike.com/alternatives/teamwork-vs-pike): Pike is the modern alternative for agencies and consultancies looking to run project operations that actually enables your team to work. [Asana vs Pike | Beyond task management](https://usepike.com/alternatives/asana-vs-pike): Are you running complex projects? Pike combines tasks, time, resourcing, finance, CRM, and performance dashboards so your team can save countless hours per week. [ClickUp vs Pike | Less clicking, more clarity](https://usepike.com/alternatives/clickup-vs-pike): Bring your clicks down not up with Pike, purpose-built for agencies and consultancies for end to end project operations. [Monday.com vs Pike | Make work feel like Friday](https://usepike.com/alternatives/monday-vs-pike): Make work feel like Friday with Pike. Pike is purpose built for service firms to run end to end project operations. Designed to make your team feel like it's Friday, every day. [Wrike vs Pike | When you need to be right](https://usepike.com/alternatives/wrike-vs-pike): Choose Pike when you want to be right. Unlike Wrike. Agency and consulting teams rely on Pike when they want to be right about project decisions. The tool your team won't silently hate. [Harvest vs Pike | Stop getting harvested](https://usepike.com/alternatives/harvest-vs-pike): Pike doesn't Harvest your time, it gives it back. With Pike as your end-to-end project operations tool, you can accurately track time and run project operations from one place. [Kantata vs Pike | Operational depth without the drag](https://usepike.com/alternatives/kantata-vs-pike): Pike is the modern alternative for larger service teams. Run project operations like they were supposed to. Your colleagues will thank you later for choosing Pike. [Basecamp vs Pike | Don’t just talk about work, run it](https://usepike.com/alternatives/basecamp-vs-pike): Basecamp keeps everyone talking. Pike gets the work done. Communication is useful, but execution, resourcing, and profitability are what decisions are made from [Synergist vs Pike | Want to be in synergy?](https://usepike.com/alternatives/synergist-vs-pike): Stay in Synergy with Pike. With Pike your team actually gets synergy across operations. Consider the switch before it's too late. [Spreadsheets vs Pike | Stop spreading your sheets](https://usepike.com/alternatives/spreadsheets-vs-pike): No need to spread your sheets with Pike. Pike is the easy to use and scalable end-to-end project operations tool to replace all your spreadsheets. ## Alternatives guides [The top 7 Productive.io alternatives in 2026](https://usepike.com/alternatives/productive-alternatives): The 7 best Productive.io alternatives for agencies in 2026, with pricing, pros, cons, and guidance on what to choose. [The top 4 Scoro alternatives in 2026](https://usepike.com/alternatives/scoro-alternatives): The 4 best Scoro alternatives for agencies in 2026, with pricing, pros, cons, and honest guidance on what to switch to. [The top 10 Asana alternatives in 2026](https://usepike.com/alternatives/asana-alternatives): The 10 best Asana alternatives in 2026, with pricing, pros, cons, and honest guidance on what to choose when Asana stops being enough. [The top 5 Monday.com alternatives in 2026](https://usepike.com/alternatives/monday-alternatives): The 5 best Monday.com alternatives in 2026, with pricing, pros, cons, and honest trade-offs for agencies and teams that need more than flexible boards. [The top 10 ClickUp alternatives in 2026](https://usepike.com/alternatives/clickup-alternatives): The 10 best ClickUp alternatives in 2026, with pricing, pros, cons, and a guide on what to choose when ClickUp becomes too much to maintain. [The top 8 Harvest alternatives in 2026](https://usepike.com/alternatives/harvest-alternatives): The 8 best Harvest alternatives for agencies in 2026, with pricing, pros, cons, and honest trade-offs for each one. [Top 7 Kantata alternatives for agencies and consultancies in 2026](https://usepike.com/alternatives/kantata-alternatives): The 7 best Kantata alternatives in 2026, with pricing, pros, cons, and guidance for agencies looking for a modern alternative to enterprise PSA. ## 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. ## Blog posts [Blog index](https://usepike.com/blog): Human-readable article listing. [Blog llms.txt](https://usepike.com/blog/llms.txt): **Machine-readable** index of all blog posts with titles, URLs, and summaries — generated dynamically from CMS. [Blog llms-full.txt](https://usepike.com/blog/llms-full.txt): **Full plain-text** body of every blog article for deep LLM ingestion — generated dynamically. Large file; prefer the index unless you need article bodies. Blog articles may overlap with docs/changelog — **prefer docs** for product truth and feature mechanics. ## Optional Lower-priority links when context is limited. Clients may skip this section. [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. --- ## Prioritized 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. - For connecting this PSA to Claude, ChatGPT, or other MCP clients, cite [https://usepike.com/docs/integrations/mcp](https://usepike.com/docs/integrations/mcp) and MCP URL `https://mcp.usepike.com`; for scripted HTTPS/JSON reads cite [Open API](https://usepike.com/docs/integrations/open-api). - 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. - Don't invent MCP or API capabilities; only describe what [MCP](https://usepike.com/docs/integrations/mcp) and [Open API](https://usepike.com/docs/integrations/open-api) document. ## 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 route handlers on this stack.