// Service pages: one per pillar, all rendered from SERVICE_PAGES.
// Examples are written in the present tense as things we build. Do not add client names, results, statistics, or past-tense claims of delivered work.

const SERVICE_PAGES = {
  'ai-strategy-roadmap': {
    title: "AI strategy and roadmap",
    profile: { fit: "Leadership teams that want a plan before spending on tools", first: "A ranked roadmap with a clear first step", leads: "Amanda Rinderle or Jonas Clark, with your CEO and leadership team" },
    headline: "Know which AI projects will pay off, and in what order.",
    lede: "We work out where AI will pay off in your organization and in what order. You get a short, ranked roadmap, a view of what your data can support today, and a clear first step, whether or not we build it.",
    problem: [
      { h: "Everyone has an opinion about AI.", p: "Vendors, staff, and board members each have a favorite idea, and nobody has ranked them." },
      { h: "We don't know where to start.", p: "The list of possible projects is long, and some depend on data that may not be in usable shape." },
      { h: "We bought tools and few people use them.", p: "Licenses went to a team with no time to learn them and no clear job for them to do." },
      { h: "AI is on the agenda, but nobody owns it.", p: "Leadership wants a plan, but no one has the time or the background to write one." },
    ],
    does: [
      { h: "Map how the work runs", p: "We talk to the people who do the work and trace how orders, jobs, and decisions move through the organization, including the spreadsheets and email threads in between." },
      { h: "Test what your data can support", p: "We look at your records and tell you which ideas they can support now, which need cleanup first, and which should wait. We also work out which of your data is sensitive or controlled and where outside AI tools may and may not be used, so the roadmap respects those limits." },
      { h: "Rank the opportunities", p: "Each idea is rated on value, effort, and risk, so the roadmap is short and ordered and not a wish list." },
      { h: "Write the roadmap", p: "A plain written plan covering what to do first, who owns it, what it needs, and what to leave alone for now." },
    ],
    examples: [
      "We deliver a ranked roadmap of the AI projects most likely to pay off, with a plain-language case for each.",
      "We assess what your data can support today and what has to be cleaned up before a project could work.",
      "We map which of your data is sensitive or controlled and set where AI tools may and may not be used, so the first projects stay inside those lines.",
      "We run a working session with your leadership team to choose the first project and name its owner.",
    ],
    first: "You tell one of the partners where the work feels slow or expensive and what you've already tried. We'll ask what you'd want to be true a year from now.",
    engagementIntro: "Start with the map.",
    engagementNote: "The roadmap is usually a fixed-scope project. From there you can build with us, build with someone else, or wait.",
    suits: [
      "This suits companies and institutions of any size where leadership wants a plan before spending on tools.",
      "It also suits teams that have bought tools and want to know whether to keep going.",
    ],
    industries: ['manufacturing', 'wholesale-distribution', 'insurance-banking', 'professional-services'],
    related: ['ai-training-adoption', 'business-operations'],
    institutions: true,

    firstProject: [
      "A written roadmap that ranks the candidate projects. Each one has an owner and a list of what it needs.",
      "Notes on which ideas your records can support today and which need cleanup first.",
      "A list of the data that is sensitive or controlled, and where outside AI tools may be used with the rest.",
      "A working session in which your leadership team picks the first project.",
    ],
    faq: [
      { q: "Why not just use ChatGPT or Claude ourselves?", a: "You should, for plenty of things. Drafting, summarizing, and one-off analysis work well in a chat tool. A roadmap answers which projects are worth building across the organization, and most of that work happens in your records and systems. We check whether an idea has the data it needs, what it would have to connect to, and which data has to stay out of outside tools." },
      { q: "What data do you need to see first?", a: "Often nothing at the start. If a sample would change the recommendation, we ask for something small, like an order export or a few dozen documents, and talk with you about what is in it before you send it." },
      { q: "Do we have to build with you afterward?", a: "No. The roadmap is written for whoever builds it, whether that is us, another firm, or your own staff." },
      { q: "What if our data is not in good shape?", a: "Most organizations have some of that. The roadmap marks which projects your records support now and which need cleanup first, and the cleanup goes into the order." },
      { q: "Who does the work?", a: "The partners. The people on the first call are the ones who run the interviews, read the data, and write the roadmap." },
    ],
    closer: {
      heading: "Tell us where the work feels slow or expensive.",
      text: "The first conversation is twenty minutes and free. Tell us what you have tried so far. If something smaller than a roadmap would do, we will say so.",
    },
  },

  'ai-training-adoption': {
    title: "AI training and adoption",
    profile: { fit: "Organizations where staff already use AI informally", first: "One team, trained on its own documents and tasks", leads: "Amanda Rinderle or Jonas Clark, with your CEO or executive director and the team's manager" },
    headline: "Your team, using AI on the work they already do.",
    lede: "We train your people to use AI on their own work, one role at a time, and help the organization settle on the tools, rules, and habits that make it routine.",
    problem: [
      { h: "People are using AI on their own.", p: "Staff experiment with personal accounts and have no guidance on what data is safe to share." },
      { h: "One workshop, then nothing changes.", p: "A general session on AI tools doesn't touch the specific tasks people do each day." },
      { h: "Leaders and staff aren't aligned.", p: "Leaders want results, staff worry about their jobs, and nobody has said plainly what AI is for here." },
      { h: "There are no rules yet.", p: "No one has written down which tools are approved, what may be pasted into them, and who to ask." },
    ],
    does: [
      { h: "Train by role", p: "We build short sessions around the tasks of each role, using your own documents and examples, so people practice on real work." },
      { h: "Set the ground rules", p: "We help you write a plain usage policy covering approved tools, which data is sensitive or controlled and where it may go, and review of anything that goes out." },
      { h: "Pick and set up the tools", p: "We recommend a small set of tools, configure them, and connect the ones that need your data." },
      { h: "Build the habit", p: "Follow-up sessions, office hours, and a few internal champions keep the use going after the first week." },
    ],
    examples: [
      "We run role-based sessions for sales, operations, and finance, each built around that team's own documents and tasks.",
      "We write the usage policy with your leadership, so staff know which tools to use and what data stays out.",
      "We train a few champions in each department to coach colleagues and collect what's working.",
    ],
    first: "You tell one of the partners which teams would benefit most and what worries people. Have your current tool list and any existing policy handy.",
    engagementIntro: "Start with one team.",
    engagementNote: "We usually begin with one team and a handful of its real tasks, then extend to the others. Training can be a fixed-scope program or monthly sessions over several months.",
    suits: [
      "This suits organizations where AI is already in use informally and leaders want it done safely and well.",
      "It also suits institutions with stretched staff who are cautious about new tools.",
    ],
    industries: ['professional-services', 'insurance-banking', 'healthcare', 'manufacturing'],
    related: ['ai-strategy-roadmap', 'business-insight'],
    institutions: true,

    firstProject: [
      "Sessions for one team, built from that team's own documents and recurring tasks.",
      "A draft usage policy for your leadership to review. It covers approved tools, what can be pasted into them, and who checks work before it goes out.",
      "The team's tools set up, with access to company data only where a task needs it.",
      "Two or three people on the team trained to answer their colleagues' questions.",
    ],
    faq: [
      { q: "Why not just use ChatGPT or Claude ourselves?", a: "That is usually where training starts. Your people are probably using a chat tool already, some of them on personal accounts. The sessions settle which accounts are approved, what can go into them, and which tasks in each role they suit. Where a tool needs company data, we set it up on a business account with access rules." },
      { q: "What do you need to see first?", a: "Three or four real tasks from the team, like last month's report or a typical customer email thread. The exercises are built from those. You decide what is too sensitive to use, and we work around it." },
      { q: "Does this replace our people?", a: "Training is aimed at the staff you have now and the tasks they already do. Future staffing is your decision, and it is outside what we advise on here." },
      { q: "What about staff who are worried about AI?", a: "We raise it in the first session. The worries are usually about jobs and about who is responsible when the tool is wrong. We can answer the second one: the person who sends the work is responsible for it, and the sessions cover how to check it. The first is for your leadership to answer, ideally before training starts." },
      { q: "What if people stop using it after the sessions?", a: "Some will. Use tends to fade when the tool is not tied to a specific task, so each session ends with one task people agree to try that week. The follow-up sessions show who has stopped and why." },
    ],
    closer: {
      heading: "Tell us which team to start with.",
      text: "Bring your current tool list and any policy you have, even a draft. We will spend the twenty minutes on what that team does each week.",
    },
  },

  'business-operations': {
    title: "Business operations",
    profile: { fit: "Companies where work still runs through email, spreadsheets, and a few key people", first: "One working tool on the workflow that takes the most hours, often quoting or order entry", leads: "Amanda Rinderle or Jonas Clark, with your CEO and the people who run that workflow" },
    headline: "Fewer steps between an order and an invoice.",
    lede: "We look at how work moves through your company and find the steps AI can take over. Then we build the tools, connect your systems, and train your team to run them.",
    problem: [
      { h: "Every job lives in its own spreadsheet.", p: "To see the whole schedule, someone walks the floor or makes a few calls." },
      { h: "Quotes wait on one person.", p: "One or two people know how to price the work. When they're out, quotes sit." },
      { h: "We key the same order in three places.", p: "Orders, invoices, and inventory live in separate tools, and someone copies between them by hand. The mistakes surface when the books don't reconcile." },
      { h: "Everyone is trying AI on their own.", p: "People paste company data into whatever tool they found. Nobody has said which uses are fine." },
    ],
    does: [
      { h: "Map the work", p: "We follow one quote, order, or job from the first email to the invoice and write down every handoff. AI usually fits where someone retypes information or chases a reply." },
      { h: "Build the tools", p: "We build assistants and automations for those steps. A quote gets drafted from similar past jobs, or an emailed purchase order gets read into the system. Anything going to a customer waits for a person to approve it. If software you already own can do the job, we turn that on instead." },
      { h: "Connect your systems", p: "We connect the tools your team already uses so information is entered once. Usually that takes a handful of integrations, and no new platform." },
      { h: "Train your team", p: "We train the people who will use each tool, one role at a time, on their own work. Every tool has a named owner on your side." },
    ],
    examples: [
      "We connect your order inbox, your ERP, and your pricing, so a purchase order that arrives overnight is entered, priced, and waiting for approval in the morning.",
      "We build the agent that works your open orders each morning. It checks stock and ship dates, chases suppliers for confirmations, and flags the orders that slipped.",
      "We build the briefing your managers read first, put together from every system overnight: what shipped, what is late, and what needs a decision.",
    ],
    first: "You tell one of the partners how a typical order or job moves through the company, and where it waits. We'll have questions before we have suggestions.",
    engagementIntro: "Start with one workflow.",
    engagementNote: "We usually pick the workflow that eats the most hours each week, often quoting or scheduling. Once it runs without anyone watching it, we add the next.",
    suits: [
      "This suits companies where work still moves through email, spreadsheets, and a few key people, whether that is a single plant or one division of a large company.",
      "It also suits companies with an ERP that still run quoting, scheduling, or purchasing on spreadsheets and email.",
    ],
    industries: ['manufacturing', 'wholesale-distribution', 'construction-trades', 'professional-services'],
    related: ['business-insight', 'product-supply-chain'],

    firstProject: [
      "A working tool on one workflow, such as quoting or order entry. A person approves anything it sends outside the company.",
      "A map of that workflow from the first email to the invoice, with each handoff marked.",
      "A short list of what the tool handles, what it passes to a person, and what it should not be used for.",
      "Training for the people who use it, and a named owner on your side.",
    ],
    faq: [
      { q: "Why not just use ChatGPT or Claude ourselves?", a: "A chat tool can draft one email well. It can't see the orders in your ERP, compare a price with similar past jobs, or enter the result back into the system. Most of what we build is that connection. We test it on your past quotes and orders, send anything unusual to a person, and build in a log of what the tool produced and who approved it." },
      { q: "What data do you need to see first?", a: "Ten or twenty recent examples of the workflow, such as quotes, orders, or purchase orders, with a note on where each one waited. We run the tool against them before anyone relies on it. Customer details you would rather we not see can come out first." },
      { q: "Does this replace our people?", a: "It takes on the retyping, the chasing, and the first drafts. Pricing calls and approvals stay with the people who make them now. Staffing decisions are yours." },
      { q: "How do you handle mistakes?", a: "The tool is set up on the assumption that it will make some. Anything going to a customer waits for a person. Cases that don't look like what it was tested on go to someone instead of getting a guess. Each run is logged, so a bad number can be traced to where it came from." },
      { q: "Do we need to replace our ERP or buy a new platform?", a: "Usually not. We connect what you already run. If software you own has the feature, we turn it on and configure it before building anything." },
    ],
    closer: {
      heading: "Tell us where an order or a job waits.",
      text: "Walk us through how a typical order moves through the company. The first conversation is twenty minutes and free, and you should expect questions before suggestions.",
    },
    cases: [
      { id: 'revere', client: 'Revere Auctions', tag: 'Business', image: 'assets/revere-hero.jpg', services: ['Business operations'], desc: 'A suite of proprietary AI tools and systems behind Revere\'s daily operations, from photo and barcode listing to marketplace dashboards, invoicing, and inventory, built and run with Revere since 2019.' },
    ],
  },

  'business-insight': {
    title: "Business insight",
    profile: { fit: "Teams with years of records across several systems, waiting on reports", first: "Answers to your first few questions, each traced to its records", leads: "Amanda Rinderle or Jonas Clark, with your CEO and whoever owns finance or reporting" },
    headline: "Answers from your own numbers, without waiting for a report.",
    lede: "We connect your sales, customer, cost, and operational data so your team can ask questions of the numbers in natural language: which products lose money, which accounts are slipping, where costs moved. Every answer traces to the records behind it. We start by cleaning up and matching the data underneath.",
    problem: [
      { h: "The answer is in there somewhere.", p: "Sales history is in the ERP, costs are in accounting, and customer activity is in the CRM. Any question that touches all three becomes a project." },
      { h: "Margin is hard to see.", p: "What a product or a customer really earns depends on freight, returns, rebates, and discounts that sit in different systems." },
      { h: "A report takes a week.", p: "Someone asks a question on Monday and gets a spreadsheet on Friday, by which time there's a follow-up question." },
      { h: "Our systems are good, but they don't talk to each other.", p: "Each one is right about its own data. Nothing ties a customer in one system to the same customer in another." },
    ],
    does: [
      { h: "Bring the records together", p: "We copy records from your ERP, CRM, accounting, and operational systems into one store, and match the same customer across them even when it appears under a short name, a legal name, and an account number. Uncertain matches go to a person to confirm. Your systems keep running as they are, and nothing is written back to them without your say." },
      { h: "Answer questions in natural language", p: "Your team asks in everyday language and gets an answer with the source records attached, so anyone can check it." },
      { h: "Keep it current and controlled", p: "The store refreshes on a schedule. Access follows the permissions you already have, so a salesperson doesn't see payroll. Data that can't leave your network stays inside it." },
    ],
    examples: [
      "We show which products and customers make money once freight, returns, and rebates are counted.",
      "We match every customer across your CRM, ERP, and accounting system, so a question about one account gets one answer.",
      "We build the reports leadership reads each week, refreshed on a schedule and traceable to the records behind them.",
    ],
    first: "Bring a short list of questions you wish you could answer and can't. We'll ask where the records for each one live.",
    engagementIntro: "Start with a few hard questions.",
    engagementNote: "We pick a handful of questions that matter to you, connect only the systems that hold the answers, and build out from there. If your records can't support forecasting yet, we tell you and build the record first.",
    suits: [
      "This suits companies and institutions with years of records across several systems and teams that wait on reports.",
      "Business insight is the data layer. What your organization knows beyond the numbers, such as decisions, documents, and how work gets done, is Organizational intelligence.",
    ],
    industries: ['manufacturing', 'wholesale-distribution', 'insurance-banking', 'professional-services'],
    related: ['organizational-intelligence', 'business-operations'],

    firstProject: [
      "One store holding the records behind your first few questions, with the same customer matched across your systems.",
      "A way for your team to ask those questions in natural language and see the source records under each answer.",
      "A list of the matches a person confirmed and the gaps the data could not fill.",
      "Access based on the permissions you already have, and a session for the people who will use it.",
    ],
    faq: [
      { q: "Why not just use ChatGPT or Claude ourselves?", a: "Paste an export into a chat tool and it will summarize it well. Ask it which accounts bought less this year than last and it has nothing to go on. It can't see your ERP, and it can't tell that Acme, Acme Corp., and account 10442 are the same customer. We connect the systems, match the records, and set access so people see only what they are allowed to. Before anyone relies on it, we test it on questions you already know the answers to." },
      { q: "What data do you need to see first?", a: "Your list of questions first. Then read-only exports from the systems that hold the answers. Systems the first questions don't touch stay out of it." },
      { q: "What happens to the sensitive data?", a: "Access follows the permissions you already have, and data that can't leave your network stays on it. Before we build, we work out with you where the store is hosted, who can reach it, and how long records are kept." },
      { q: "How do you handle mistakes?", a: "Every answer lists the records it came from, so a wrong one can be traced. Matches the tool isn't sure of go to a person. Some questions it will answer badly, often ones your data was never collected to answer, and we tell you which." },
      { q: "Do our existing systems change?", a: "No. We read from them. Nothing is written back unless you ask for it." },
    ],
    closer: {
      heading: "Tell us what you wish you could answer.",
      text: "Bring three or four questions you can't answer today. We will ask where the records for each one live, and whether those records agree with each other.",
    },
  },

  'product-supply-chain': {
    title: "Product and supply chain intelligence",
    profile: { fit: "Companies whose products come from many parts or many suppliers", first: "One product line or bill of materials, mapped to its suppliers", leads: "Amanda Rinderle or Jonas Clark, with your CEO and purchasing or engineering leads" },
    headline: "See supplier risk and tariff exposure before they reach your margin.",
    lede: "We build a searchable record of your products and suppliers, including bills of materials, costs, and sourcing. It flags end-of-life parts, tariff exposure, and supplier risk, and it stays current.",
    problem: [
      { h: "We don't really know what's inside what we sell.", p: "The bill of materials is incomplete or out of date, and some parts have no clear source." },
      { h: "A part went end-of-life and we found out late.", p: "The last-time-buy notice reached one person's inbox, and nobody was tracking lifecycle across the whole parts list." },
      { h: "A tariff changed and we can't tell what it touches.", p: "Country of origin isn't recorded for each product, so answering means a manual review." },
      { h: "The same supplier appears under three names.", p: "Vendor records came in at different times and in different formats, so spend and risk for one supplier are split across the duplicates." },
    ],
    does: [
      { h: "Build the product record", p: "We pull part numbers, bills of materials, costs, and supplier links into one searchable record and match the same part across your systems. Uncertain matches go to a person. For products you didn't design, we can start from a teardown and identify the components." },
      { h: "Watch for risk", p: "The record flags parts that are end-of-life or close to it, components with a single source, lead times that are getting longer, and tariff exposure by country of origin." },
      { h: "Find and compare suppliers", p: "When a part needs a second source, the tools research candidates before anyone picks up the phone. Quotes from different suppliers are put on the same basis so you can compare them." },
      { h: "Keep it current", p: "On a schedule, the record checks for lifecycle notices, lead-time changes, and tariff updates. Someone on your team owns it, and we can keep it running as monthly support." },
    ],
    examples: [
      "We build a record of every component and supplier in your products, kept current as lifecycle notices, lead times, and tariff rules change.",
      "We watch your suppliers and the trade rules that affect them every day, and tell you which products an issue touches before it reaches your customers.",
      "When a part or a supplier goes away, we research alternatives and set their quotes side by side, so you decide with the facts in front of you.",
    ],
    first: "You walk one of the partners through what you sell, where it comes from, and what you track today. Have a bill of materials or a vendor list open if you can.",
    engagementIntro: "Start with the record.",
    engagementNote: "Forecasting needs a clean record to learn from. If yours isn't there yet, we say so and build it first. Building the record is usually a fixed-scope project, and keeping it current suits monthly support.",
    suits: [
      "This suits manufacturers, hardware companies, distributors, and consumer brands whose products are built from many parts or bought from many suppliers.",
      "It also suits companies that sell products they didn't fully design and want to know what's in them.",
    ],
    industries: ['manufacturing', 'robotics-hardware', 'consumer-brands-retail', 'wholesale-distribution'],
    related: ['business-insight', 'sales-fundraising'],

    firstProject: [
      "A searchable record for one product line or one bill of materials, with each part matched to its supplier.",
      "Flags on that record for end-of-life parts, single-source components, and tariff exposure by country of origin.",
      "A note for each flag on where its data comes from and when it is likely to be wrong.",
      "A walkthrough with the person who will own the record on your side.",
    ],
    faq: [
      { q: "Why not just use ChatGPT or Claude ourselves?", a: "Ask a chat tool what a part does, or have it draft a note to a supplier, and it will do fine. It can't hold your bill of materials, recognize the same capacitor under three part numbers, or check manufacturers' lifecycle notices on a schedule. We build the record and the checks, test the flags against parts whose history you know, and send matches we are unsure of to a person. Changes to the record are logged with a date." },
      { q: "What do you need to see first?", a: "A bill of materials or a vendor list, in whatever shape it's in. A spreadsheet is fine, and so is a partial one. For a product you didn't design, we can start from a teardown." },
      { q: "What if our records are incomplete?", a: "Most are. Country of origin is often blank, and the same supplier shows up under different names. We show you the gaps and what each flag can and can't tell you with them. Forecasting waits until the record can support it." },
      { q: "Does this replace our buyers or engineers?", a: "No. The record does the watching, which is the part nobody has time for. What to do about a part or a supplier is still a decision for your buyers and engineers." },
      { q: "How do you handle mistakes?", a: "Each flag shows its source and the date it was last checked. A flag tells someone to look, and the decision stays with them. The note on each flag explains how it is produced, so your team can judge how much weight to give it." },
    ],
    closer: {
      heading: "Tell us what you sell and where it comes from.",
      text: "Have a bill of materials or a vendor list open if you can. We will go through it with you and ask about the parts that worry you.",
    },
  },

  'sales-fundraising': {
    title: "Sales and fundraising",
    profile: { fit: "Teams whose revenue or giving rests on a few relationships", first: "Research, drafting, and tracking for one market or donor group", leads: "Amanda Rinderle or Jonas Clark, with your CEO or executive director and your sales or development lead" },
    headline: "More of the right conversations, with less research by hand.",
    lede: "We set up AI to research prospects and donors, draft outreach, and keep track of the pipeline. The same approach works for sales and for fundraising.",
    problem: [
      { h: "Revenue depends on a few people.", p: "Selling or fundraising works because of who is doing it. When they're busy, nothing new starts." },
      { h: "We bought a CRM and nobody updates it.", p: "Follow-up depends on memory, and good leads go quiet." },
      { h: "We don't know who to call next.", p: "Researching one account properly takes an hour or two, so most of the list never gets looked at." },
      { h: "Selling has been an afterthought.", p: "The company is very good at what it makes. Nobody has written down who the best customers are or how the last ten deals started." },
    ],
    does: [
      { h: "Define the list", p: "We work out what your best customers or donors have in common, from your own records and public information, and build a list of others who fit." },
      { h: "Research each account", p: "Before a first call, the tool assembles a one-page brief from public sources and your own history with that company or donor." },
      { h: "Draft outreach", p: "The tool drafts first messages and follow-ups in your voice. Nothing goes out until someone on your team has read it and sent it." },
      { h: "Keep the pipeline", p: "It tracks who was contacted, who replied, and what happens next, in the CRM you already have or a simple one we set up." },
    ],
    examples: [
      "We find the companies or donors most like your best ones, research each, and hand you a short brief and a drafted first message to review.",
      "We prepare a brief for every meeting, covering the person, your history with them, and the questions worth asking.",
      "We keep your pipeline current by logging contacts and follow-ups from email and calendar, so nothing waits on someone remembering.",
    ],
    first: "Tell one of the partners who buys from you or gives to you today, and how the last few of those relationships started.",
    engagementIntro: "Start with one list.",
    engagementNote: "We begin with one market or one donor group and set up research, drafting, and tracking for it. When that's working, we add the next.",
    suits: [
      "This suits companies with a good product and a thin sales function, and teams whose revenue rests on a few relationships.",
      "It also suits nonprofits and institutions whose development staff are stretched.",
    ],
    industries: ['robotics-hardware', 'manufacturing', 'insurance-banking', 'professional-services'],
    related: ['business-insight', 'business-operations'],
    institutions: true,

    firstProject: [
      "A target list of customers or donors who resemble your best ones, built from your records and public information.",
      "A one-page brief on each of the first accounts, with sources cited.",
      "Outreach drafts in your voice for your team to edit and send.",
      "A pipeline view in your CRM, or a simple one we set up.",
      "A note on what the research tends to get wrong.",
    ],
    faq: [
      { q: "Why not just use ChatGPT or Claude ourselves?", a: "For a single email, go ahead. Prospecting a whole list is different work. It starts with your own history, to find out who your best customers or donors are, and then needs research that cites where each fact came from, drafts that sound like you, and a record of who has been contacted. We connect those and test them on accounts you already know well, so you can see what the tool gets right and wrong." },
      { q: "What data do you need to see first?", a: "An export of your customers or donors, with whatever you know about how each relationship started. A spreadsheet will do. Leave out anything you would rather we not see; the research works with less." },
      { q: "Will it send messages on its own?", a: "No. It drafts. Someone on your team reads, edits, and sends every message." },
      { q: "Does this replace our salespeople or development staff?", a: "No. It does the research and tracking that mostly go undone today. The conversations, and the relationships that come out of them, stay with your people." },
      { q: "What if a brief gets a fact wrong?", a: "Sometimes one will. A brief can mix up two people with the same name or lean on an old bio. Each fact links to its source so it can be checked before a call, and we test on accounts you know well to see which mistakes the tool tends to make." },
    ],
    closer: {
      heading: "Tell us who buys from you, or who gives.",
      text: "The first conversation is twenty minutes and free. Tell us how your last few relationships began. That often says more than the CRM does.",
    },
  },

  'organizational-intelligence': {
    title: "Organizational intelligence",
    profile: { fit: "Organizations with years of documents and know-how spread across systems and people", first: "The documents behind your first few questions, connected where they live", leads: "Amanda Rinderle or Jonas Clark, with your CEO or executive director and the staff who will use it" },
    headline: "Everything your organization knows, where your people and AI can use it.",
    lede: "Every organization holds years of documents, decisions, and know-how across systems, shared drives, and people's heads. We build the organization's brain: we connect policies, past proposals, job files, board materials, and history where they already live, so staff and their AI tools can draw on them and cite their sources. Business insight covers the numbers. This is the context around them.",
    problem: [
      { h: "What you know is in too many places.", p: "Policies, minutes, proposals, job files, and reports sit in shared drives, inboxes, and old systems. Nobody can ask one question across them." },
      { h: "The people who know are leaving.", p: "Long-serving staff know why a decision was made, how each customer likes to be handled, and what was tried before. Little of it is written down where anyone can find it." },
      { h: "Questions take days.", p: "A leader asks what was decided the last time something came up, and someone spends days digging through old documents to find out." },
      { h: "Your AI tools don't know your organization.", p: "Staff use chat tools that have never seen your documents, your rules, or your history, so every answer starts from scratch." },
    ],
    does: [
      { h: "Connect what you know", p: "We connect your shared drives, document systems, and core records where they sit today, and organize them so the right context can be found. Your systems keep running as they are, nothing is written back without your say, and access follows the permissions you already have." },
      { h: "Answer questions in natural language", p: "Staff ask in everyday language and get an answer with the source documents and records attached, so anyone can check it." },
      { h: "Give your AI tools your context", p: "We connect the AI tools your staff are approved to use, so a draft proposal, memo, or report starts from your own sources instead of a blank page." },
      { h: "Capture what experienced people know", p: "We work with long-serving staff to record how they decide, from past bids, cases, and correspondence, so it stays when they move on. For fundraising and membership teams, the same context supports research and outreach." },
    ],
    examples: [
      "We connect decades of job files, past bids, and correspondence, so an estimator's AI tools work from the company's own history.",
      "We give staff a way to find what was decided, when, and why, without asking the one person who remembers.",
      "We connect policies, board materials, and grant files at a college or foundation, so leadership can ask a question and get the answer with its sources.",
    ],
    first: "Bring a short list of questions you wish you could answer and can't, such as why a policy changed or how a past project was priced. We'll ask where the documents for each one live.",
    engagementIntro: "Start with a few hard questions.",
    engagementNote: "We pick a handful of questions that matter to you, connect only the folders and systems that hold the answers, and build out from there.",
    suits: [
      "This suits any organization with years of documents and know-how spread across systems and people: manufacturers, distributors, and professional firms as much as colleges, foundations, nonprofits, associations, hospitals, and public bodies.",
      "Organizational intelligence is the context layer. The numbers themselves, such as sales, margin, and customers, are Business insight.",
    ],
    industries: ['manufacturing', 'professional-services', 'insurance-banking', 'healthcare'],
    related: ['business-insight', 'ai-training-adoption'],
    institutions: true,

    firstProject: [
      "The documents and records behind your first few questions connected, and organized so the right context can be found.",
      "A way for staff to ask those questions in natural language, with the sources shown under each answer.",
      "Your approved AI tools connected to the same sources, so drafts start from your own material.",
      "Access based on the permissions your systems already enforce, and a working session with the staff who will use it.",
    ],
    faq: [
      { q: "Why not just use ChatGPT or Claude ourselves?", a: "Plenty of work fits a chat tool, like drafting a letter or summarizing a report. Questions about your own organization don't, because the tool has never seen your documents. Why did we change that policy? How did we price the last job like this? Answering those means connecting your files and records while respecting who may see what. We build those connections and test them on questions your staff can already answer by hand." },
      { q: "What do you need to see first?", a: "Start with the questions you can't answer today. After that, read-only access to the folders and systems that hold the answers. Anything the first questions don't touch stays out of it." },
      { q: "What happens to sensitive documents?", a: "Client, employee, donor, patient, and financial material each come with their own rules, and you already have people who interpret them. Before we build, we work with them on what goes in, where it is hosted, and how long it is kept. Access follows the permissions your systems already enforce." },
      { q: "Does this replace our staff?", a: "No. It lets staff find what the organization already knows without hunting through drives or asking around. Deciding what it means, and what to do about it, stays with them." },
      { q: "How do you handle mistakes?", a: "Every answer shows the sources behind it, so a wrong one can be traced. We also tell you which kinds of question it answers poorly, for example ones about decisions that were never written down." },
    ],
    closer: {
      heading: "Tell us what your organization should be able to answer.",
      text: "Bring a few questions, like why a policy changed or how a past job was priced. We will ask where the documents live and who keeps them up to date.",
    },
  },
};

function ServicePage({ setRoute, slug }) {
  const page = SERVICE_PAGES[slug];
  if (!page) return null;
  const label = (list, s) => (list.find(x => x.slug === s) || {}).label || s;

  return (
    <div data-screen-label={`Service: ${page.title}`}>
      <PageHero
        routeName="service"
        setRoute={setRoute}
        eyebrow={page.title}
        title={page.headline}
        lede={page.lede}
        image={slug}
        meta={[{ dt: 'Good fit for', dd: page.profile.fit }, { dt: 'Common first project', dd: page.profile.first }, { dt: 'Who leads', dd: page.profile.leads }]}
      />

      <section className="q-who">
        <div className="q-wrap">
          <div className="q-who-grid">
            <div className="q-section-head">
              <div className="q-eyebrow">In your words</div>
              <h2>What we hear most often.</h2>
            </div>
            <div className="q-situations">
              {page.problem.map(s => (
                <div key={s.h} className="q-situation">
                  <h3>{s.h}</h3>
                  <p>{s.p}</p>
                </div>
              ))}
            </div>
          </div>
        </div>
      </section>

      <section className="q-page-section">
        <div className="q-wrap">
          <div className="q-section-head" style={{ marginBottom: 40 }}>
            <div className="q-eyebrow">What we do</div>
            <h2>What we do about it.</h2>
            {page.proof && <p>{page.proof}</p>}
          </div>
          <NumberedList items={page.does.map(d => ({ title: d.h, body: d.p }))} />
        </div>
      </section>

      <ExampleList examples={page.examples} />

      {page.cases && page.cases.map(c => <RelatedCase key={c.id} c={c} setRoute={setRoute} />)}

      <FirstProject items={page.firstProject} alt={!page.cases} />

      <EngagementSteps intro={page.engagementIntro} note={page.engagementNote} first={page.first} />

      <section className="q-page-section">
        <div className="q-wrap">
          <div className="q-page-split">
            <div className="q-section-head" style={{ marginBottom: 0 }}>
              <div className="q-eyebrow">Fit</div>
              <h2>Who this suits.</h2>
            </div>
            <div>
              <div className="q-page-prose">
                {page.suits.map((t, i) => <p key={i}>{t}</p>)}
              </div>
              <div className="q-page-linkgroup">
                <div className="q-page-linklabel">Industries where this comes up</div>
                <div className="q-page-links">
                  {page.industries.map(s => (
                    <PageLink key={s} route="industry" param={s} setRoute={setRoute} className="qlink qlink--brass">{label(INDUSTRIES, s)} <Arrow /></PageLink>
                  ))}
                  {page.institutions && (
                    <>
                      <PageLink route="higher-ed" setRoute={setRoute} className="qlink qlink--brass">Higher education <Arrow /></PageLink>
                      <PageLink route="foundations" setRoute={setRoute} className="qlink qlink--brass">Foundations <Arrow /></PageLink>
                      <PageLink route="nonprofits" setRoute={setRoute} className="qlink qlink--brass">Nonprofits <Arrow /></PageLink>
                    </>
                  )}
                </div>
              </div>
              <div className="q-page-linkgroup">
                <div className="q-page-linklabel">Related services</div>
                <div className="q-page-links">
                  {page.related.map(s => (
                    <PageLink key={s} route="service" param={s} setRoute={setRoute} className="qlink qlink--brass">{label(SERVICES, s)} <Arrow /></PageLink>
                  ))}
                </div>
              </div>
            </div>
          </div>
        </div>
      </section>

      <FaqSection items={page.faq} idPrefix={`faq-${slug}`} />

      <PageCloser heading={page.closer.heading} text={page.closer.text} />

      <SiteFooter setRoute={setRoute} />
    </div>
  );
}

Object.assign(window, { ServicePage, SERVICE_PAGES });