> ## Documentation Index
> Fetch the complete documentation index at: https://docs.auditynow.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Build a Client POC with Lovable

> Turn an Audity audit opportunity into a live, clickable proof-of-concept app by connecting Audity and Lovable to the same Claude conversation.

Your audit found the opportunity. This recipe turns it into working software your client can click, in the same conversation, with no code.

It works by connecting two tools to one AI assistant: the **Audity connector** (your audit data and deliverables) and the **Lovable connector** (an AI app builder that deploys live apps). The assistant pulls the opportunity from Audity, writes a build brief, and drives Lovable to ship a demo at a real URL.

<Note>
  Lovable's agent connection is currently a research preview on their side, so tool names and behavior may change. This recipe was verified against Lovable's official MCP server (`mcp.lovable.dev`) as of July 2026. You need a Lovable account (free tier works; builds spend Lovable credits from your account, not Audity credits).
</Note>

## What you'll end up with

* A deployed proof-of-concept app at a `*.lovable.app` URL demonstrating one audit opportunity (an intake portal, an approval workflow, a dashboard, whatever the opportunity describes)
* Grounded in the real numbers from your audit: the client's pain points, current process, and ROI figures
* Ready to screen-share in your next client call, or iterate further in Lovable's editor

## Prerequisites

<Steps>
  <Step title="Connect Audity to Claude">
    If you haven't already: `npx @auditynow/connect`, or follow [Connect Claude](/guides/claude). Verify with "List my Audity projects."
  </Step>

  <Step title="Connect Lovable to Claude">
    In Claude's **Settings → Connectors**, add Lovable's connector (`https://mcp.lovable.dev`). Lovable uses OAuth: a browser window opens, you sign in to your Lovable account, and you're done. See Lovable's own docs for the current setup flow.
  </Step>

  <Step title="Have a project with completed analysis">
    The recipe pulls from your opportunities and ROI calculations, so run the audit first. See [Run a full audit workflow](/guides/running-an-audit).
  </Step>
</Steps>

## The recipe

<Steps>
  <Step title="Pick the opportunity">
    In a Claude chat with both connectors active:

    ```text theme={null}
    Show me the selected opportunities for my {client name} audit,
    with their ROI numbers. Which one would make the most
    convincing interactive demo?
    ```

    Claude calls `audity_get_project_opportunities` and `audity_get_roi_calculations`, then recommends. Pick one.
  </Step>

  <Step title="Generate the build brief">
    ```text theme={null}
    Write a build brief for a proof-of-concept app demonstrating
    that opportunity. Include: who uses it, the 2-3 core screens,
    the workflow it replaces (from the audit's current-process
    findings), and realistic sample data using the client's
    industry. Keep it to one screen of text. Show me the brief
    before building anything.
    ```

    Reviewing the brief before the build is the step that makes the output client-presentable instead of generic. Edit it in plain English until it matches what you'd actually pitch.
  </Step>

  <Step title="Build and deploy">
    ```text theme={null}
    Now create a new Lovable project from that brief and deploy it.
    Give me the live URL when it's done.
    ```

    Claude drives Lovable's builder (`create_project`, then deploy). First builds typically take a few minutes. You get back a live `*.lovable.app` URL.
  </Step>

  <Step title="Iterate">
    Look at the deployed app, then refine in the same chat:

    ```text theme={null}
    The dashboard should lead with the {metric} we quantified in
    the ROI calc. Change the placeholder company name to
    {client name}. Redeploy.
    ```

    You can also open the project at lovable.dev and continue in their editor directly.
  </Step>
</Steps>

## A worked example prompt

Everything above in one message, for when you know exactly what you want:

```text theme={null}
From my Audity project for {client name}, pull the top selected
opportunity and its ROI calculation. Draft a one-page build brief
for a POC app that demonstrates it (users, 2-3 screens, the manual
process it replaces, sample data in their industry). Show me the
brief and wait for my OK. After I approve, create a Lovable project
from the brief, deploy it, and give me the live URL.
```

## Tips

* **Always review the brief before building.** The demo is only as sharp as the brief; thirty seconds of editing beats a regenerate.
* **POC means POC.** Position it to the client as a directional demo, not production software. It has sample data and no real integrations.
* **Data stays illustrative.** Have Claude use realistic sample data, not real client records. The Lovable app is hosted outside Audity.
* **Costs land on your Lovable plan.** Builds spend Lovable credits; nothing in this recipe spends Audity credits.
* **Keep the audit as the anchor.** The strongest close pairs the live demo with the deliverables it came from: the [final report and deck](/guides/running-an-audit) carry the numbers, the POC makes them tangible.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Claude only sees one of the two connectors">
    Check Settings → Connectors and confirm both Audity and Lovable show as connected in the current chat. Some clients require enabling connectors per-conversation.
  </Accordion>

  <Accordion title="Lovable asks me to sign in again">
    Lovable's connection uses OAuth sessions that can expire. Re-authorize the Lovable connector and retry; your Audity connection is unaffected.
  </Accordion>

  <Accordion title="The generated app is generic or misses the point">
    Skipping the brief-review step is the usual cause. Regenerate the brief, add the specific workflow and metric that made the opportunity compelling, and rebuild.
  </Accordion>

  <Accordion title="Audity tools return 403">
    Your token may lack scopes or your plan may not include the operation. See [Connect Claude → Troubleshooting](/guides/claude#troubleshooting).
  </Accordion>
</AccordionGroup>

## What's next

* [Run a full audit workflow →](/guides/running-an-audit)
* [Guided Audit Conductor →](/guides/audit-conductor)
* [Lead conversion playbook →](/guides/lead-conversion)