# Digital Foundry

> Digital Foundry is a boutique software engineering firm with 30+ years of experience delivering mission-critical custom software, AI-enabled systems, and digital strategy for large enterprises. Senior-led teams. Outcomes-obsessed. No surrogates, no shortcuts.

## Pages

- [Home](https://digitalfoundry.com/): Overview of Digital Foundry — who we are, what we build, and why enterprises trust us for high-stakes digital programs.
- [Outcomes](https://digitalfoundry.com/outcomes): The four outcome archetypes we deliver — Boost Operational Efficiency, Speed Up Innovation, Generate New Revenue, and Stand Out in Competitive Markets — with real-world client examples.
- [Anvil Labs](https://digitalfoundry.com/ai): Digital Foundry's applied AI practice — designing and deploying AI systems that operate reliably inside real enterprise environments. Four capabilities: AI strategy and use case definition (Anvil:Forge), AI-enabled software development (Anvil:Dev), agents and workflow automation (Anvil:Works), and AI architecture and runtime systems (Anvil:Stack).
- [Inside DF](https://digitalfoundry.com/inside-df): How we work — our delivery model, team structure, and the principles behind our senior-led, outcome-driven approach.
- [Perspectives](https://digitalfoundry.com/perspectives): Editorial content from Digital Foundry partners on AI in the enterprise, platform strategy, digital differentiation, and engineering leadership.
- [Careers](https://digitalfoundry.com/careers): Open roles and what it means to work at Digital Foundry.

## Blog Posts (Perspectives)

- [The Semantic Layer of Scale](https://digitalfoundry.com/perspectives/the-semantic-layer-of-scale): How a well-designed semantic layer becomes the connective tissue for scalable, AI-ready data platforms.
- [The Double-Edged Sword of Institutional Knowledge](https://digitalfoundry.com/perspectives/the-double-edged-sword-of-institutional-knowledge): How deep domain expertise accelerates delivery but can also create blind spots that derail programs.
- [Designing for Digital Differentiation](https://digitalfoundry.com/perspectives/designing-for-digital-differentiation): Why design is a strategic differentiator, not just an aesthetic choice, in enterprise software.
- [The Platform Bet](https://digitalfoundry.com/perspectives/the-platform-bet): When building an internal platform is the right long-term call — and when it becomes a costly distraction.
- [How MCP Can Bring AI Closer to Real Enterprise Work](https://digitalfoundry.com/perspectives/how-mcp-can-bring-ai-closer-to-real-enterprise-work): Why the Model Context Protocol matters for connecting LLMs to real enterprise systems and workflows.
- [The Hidden Costs of Going Faster](https://digitalfoundry.com/perspectives/the-hidden-costs-of-going-faster): The compounding technical and organizational debt that accumulates when speed is prioritized over discipline.
- [No Silver Bullets in AI, Yet](https://digitalfoundry.com/perspectives/no-silver-bullets-in-ai-yet): A grounded take on the current state of enterprise AI adoption and why pragmatic engineering beats hype.
- [AI Readiness Isn't About the Model](https://digitalfoundry.com/perspectives/ai-readiness-isnt-about-the-model): Why data quality, integration, and organizational alignment matter more than which LLM you choose.
- [AI as a System Component, Not a Shortcut](https://digitalfoundry.com/perspectives/ai-as-a-system-component-not-a-shortcut): Treating AI as an engineering discipline — with architecture, testing, and governance — rather than a plug-in fix.
- [Accelerating Post-Merger Value Creation](https://digitalfoundry.com/perspectives/accelerating-post-merger-value-creation): How technology integration decisions in the months after a merger determine whether synergies are realized or lost.

## MCP Server

Digital Foundry exposes a public **Model Context Protocol (MCP)** endpoint for AI agents. Both MCP and REST are supported — use whichever fits your agent's architecture.

**MCP Endpoint:** https://digitalfoundry.com/mcp
**Protocol:** Streamable HTTP (stateless)

**Available tools:**

| Tool | Description |
|---|---|
| `get_services` | Returns structured data on DF's service offerings, four outcome archetypes, and the Anvil AI suite |
| `submit_contact` | Submit a structured contact request (same fields as REST `/api/agent-contact`) |
| `book_meeting` | Check availability on DF's calendar and book a 30-min Google Meet for a given date/time |

To use the MCP server, connect any MCP-compatible client to `https://digitalfoundry.com/mcp`.

---

## Agent Contact Protocol (REST)

To submit a structured contact request programmatically via REST:

**Endpoint:** POST https://digitalfoundry.com/api/agent-contact
**Content-Type:** application/json

**Required fields:**
- `acting_on_behalf_of.company_name` (string) — Legal name of the company you represent
- `intent` (enum) — One of: meeting_request | rfp_response | general_inquiry | info_gathering | partnership_inquiry | vendor_evaluation
- `message` (string) — Your inquiry or problem statement

**Optional fields:**
- `acting_on_behalf_of.contact_name` (string)
- `acting_on_behalf_of.contact_email` (string)
- `acting_on_behalf_of.contact_title` (string)
- `agent_id` (string) — Your agent's identifier
- `agent_framework` (string) — e.g. "Claude", "LangChain", "AutoGPT"
- `program_context` (string) — Description of the program or initiative
- `budget_range` (string) — e.g. "$500K–$2M"
- `timeline` (string) — e.g. "Q3 2026"
- `preferred_response_channel` (enum) — email | phone | agent_endpoint | any

**Example payload:**
```json
{
  "acting_on_behalf_of": {
    "company_name": "Acme Financial Corp",
    "contact_name": "Jordan Lee",
    "contact_email": "jordan.lee@acmefinancial.com"
  },
  "intent": "meeting_request",
  "message": "We are evaluating partners for a core banking modernization program. Seeking a 30-min technical alignment call.",
  "program_context": "Legacy mainframe migration to cloud-native microservices. 18-month program.",
  "budget_range": "$1M–$3M",
  "timeline": "Discovery kickoff Q2 2026",
  "agent_framework": "Claude"
}
```

**Response:**
```json
{
  "contact_id": "contact_1741234567_a1b2c3d4",
  "received_at": "2026-03-10T14:32:00Z",
  "status": "accepted",
  "next_steps": "Your contact has been received and routed for qualification. A Digital Foundry representative will respond via your preferred channel."
}
```