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

# Goals and results

> Give the Co-founder targets to work toward, and check its track record.

Tell the Co-founder what you're aiming for and it ranks its recommendations by what moves you toward it. Then check whether its advice actually worked.

***

## Goals

Add goals in **Settings → Goals**. Each goal has a metric, a target and a deadline (3, 6, 9 or 12 months out, or a date you pick), for one app or the whole company.

| Metric | Updated |
| - | - |
| **MRR** | Automatically, from App Store Connect and RevenueCat |
| **Revenue (7d)** | Automatically, after each run |
| **Downloads** | Automatically, after each run |
| **DAU**, **LTV : CAC**, **Custom** | By you |

The Co-founder tracks your pace and projects whether you'll hit the target. When a goal falls behind, the briefing says so and its suggestions shift toward closing the gap. Goal progress is also on the **Overview**.

***

## Commitments

When you tell the Co-founder you'll do something — "I'll ship the paywall test by Friday" — it records the commitment and follows up in later briefings. You can also add commitments yourself in **Settings → Commitments**, or from the to-dos in a briefing, and mark them done.

***

## Unit economics and runway

In **Settings → Finance**, enter your cash on hand and monthly costs. The Co-founder combines them with your revenue and ad spend to work out CAC, LTV, payback, burn and runway.

Set two alert thresholds: a **runway floor** and a **payback ceiling**, in months. The briefing warns you when you cross either.

> [!TIP]
>
> Don't want revenue in your briefings? Turn on **Leave revenue out** in **Settings → Agent**. See [Briefings](https://docs.appeeky.com/docs/cofounder/briefings.md#shape-the-briefing).

***

## Track record

| Page | What it shows |
| - | - |
| **Decisions** | Every action the Co-founder proposed, what you decided, and what happened next when it could be measured |
| **Evals** | What the Co-founder predicted vs what actually happened after a change shipped |
| **Scorecard** (on **Decisions**) | How many actions were applied, waiting or rejected, how many were measured, and how many moved the metric the right way |

The Co-founder uses these results itself: it learns which kinds of actions you apply and which tend to work, and leans on those in future briefings.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.