Founder quarterly strategy review

What is this for?

The founder quarterly strategy review is a once-a-quarter audit that gives a business owner a defensible read on the whole quarter without sitting in the day-to-day. Where the weekly and monthly checks keep you informed, the quarterly review is where you make decisions. It answers four questions: whether the site is earning its keep, whether the team is functioning without you, whether the platform is reliable, and whether the plan tier still fits.

You answer it from five screens you already know — Dashboard, Audit Log, Users, Backups, and Settings → Billing. Each screen owns one part of the picture. The Dashboard tells you whether the site performed. The Audit Log and Users tell you whether the team carried the work. Backups tells you whether the platform held. Settings → Billing tells you whether you are on the right plan for where the business is going. Put together, they produce one paragraph any stakeholder can read.

This is a quarterly site audit for a founder, not a feature walkthrough. The point is not to learn what each screen does — you already know that from the weekly and monthly checks. The point is to step back far enough to see the quarter as a trend and make the few decisions only the owner can make.

Good use cases

• The standing quarterly cadence. Block 2 hours at the end of each quarter and run the four-question check the same way every time, so the trend is comparable quarter to quarter.
• Before an investor or board update. The three founder KPIs — traffic trend, critical alerts, backup success rate — are exactly what a stakeholder summary needs, pulled straight from SGEN rather than reconstructed from memory.
• Before a plan-tier decision. When you are deciding whether to upgrade or right-size your plan, this review gives you the usage evidence (users, sites, storage against your limits) to make the call.
• After a quarter that felt off. If the quarter felt quiet, distracted, or chaotic, the Audit Log and Dashboard tell you whether the feeling matches the data — a gap in logged activity, a flat traffic line, a run of missed backups.

What NOT to use this for

• Not a weekly fix-it pass. This review is for trend and decision, not for clearing the week's noise. Use the weekly pulse for that.
• Not a hands-on settings session. You read settings here; you do not change them. Plan, backup-schedule, and integration changes are your platform administrator's to execute once you have decided the direction.
• Not a per-page content review. You are reading the quarter as a whole. Page-level editing and campaign tuning belong to your content lead and marketing manager.

How this connects to other features

• Founder weekly and monthly site checks are the recurring routines this quarterly audit sits on top of — same five screens, longer time window, decision focus.
• Site Dashboard supplies the traffic trend and the three founder KPIs you summarise for stakeholders.
• Audit Log is where you confirm consistent team activity and spot unplanned Settings-level changes across the quarter.
• Create and restore backups is where you confirm the backup schedule held for the full quarter.

Before you start

• You need Administrator access, or a role that can read Dashboard, Audit Log, Users, Backups, and Settings → Billing. If you cannot open all five, ask your platform administrator to grant read access before the session.
• Block an uninterrupted 2 hours — this is a thinking session, not a quick scan.
• Have last quarter's one-paragraph summary on hand, if you wrote one, so the trend is comparable.
• Decide who receives the output before you start — investor update, board slides, partner report — so you write the summary once, for the right reader.

Where to find it

This review is run across five existing SGEN screens — there is no single "quarterly review" page. You will open them in order, and each one answers one part of the four-question check.

Open Dashboard for the traffic trend. Open Audit Log for the quarter's activity and any unplanned settings changes. Open Users for the team roster. Open Backups for the schedule's reliability. Open Settings → Billing for the plan-tier read. The path to the plan-tier screen is Settings → Billing:

How to run the founder quarterly strategy review

Once per quarter, block 2 hours. This is not a feature review. It is a strategic audit. You are asking four questions.

1. Is the site performing at the level the business needs?

Pull the Dashboard for the quarter. Look at the traffic trend across 90 days. If traffic is flat or declining, your marketing manager and content lead need to explain why and propose a plan. If traffic is growing, confirm it is the right traffic — not volume for its own sake.

A quarter of healthy, content-led growth — traffic climbing steadily across the three months — reads like this on the Dashboard trend.

Traffic trend — last 90 days. Monthly events for Q1, pulled from the Dashboard.

The shape matters more than any single number. A line that climbs across the quarter is growth. A flat line is a plateau worth a conversation. A line that dips in the final month is the one to ask about while it is still recent.

Read the trend, not the last data point. A single strong month at the end of a flat quarter is not yet a trend — it is one month. A single weak month at the end of a strong quarter is the early warning you want to catch now, not next quarter. When the line climbs, ask the harder question your business cares about most: is this the right traffic? Volume that converts — sign-ups, enquiries, sales — is worth more than volume that bounces, and the Dashboard trend alone does not tell you which you have. Pair the traffic line with whatever conversion signal your business tracks before you call the quarter a win.

See Site Dashboard for the traffic tile and the date-range control.

2. Is the team working without my involvement?

Open Audit Log for the quarter. If you see a gap — a week or two where almost no actions were logged — the team paused for a reason. Ask. If the pause was planned (holiday, sprint boundary), fine. If it was unplanned, the content calendar needs attention.

A quarter of consistent team activity, grouped by action type, reads like this. Across the quarter the Audit Log recorded 118 logged actions — 86 Content, 9 Settings, 7 Users, and 0 Security.

The signal you care about is even spacing. You want actions in every month, with no two- or three-week stretch where the log goes silent. A gap is not automatically a problem — but it is always a question.

A planned pause is fine: a team holiday, a sprint boundary, a deliberate freeze before a launch. An unplanned pause is the one to dig into. It usually means something slipped — a deadline, a hire, a hand-off that did not happen — and the sooner you see it, the cheaper it is to fix. The Audit Log will not tell you why the gap happened. It only tells you that it did, and which weeks to ask about. Take that to your content lead as a question, not an accusation, and let them fill in the why.

See Audit Log for the action-type filter and the date-range control.

While you are in the roster, confirm Users reflects your current team — no stale contractor accounts, no role mismatches for staff whose responsibilities changed during the quarter. The roster shows 7 accounts — 5 staff and 2 contractors.

If a contractor whose engagement ended this quarter still shows an Editor or Administrator role, that is a loose end — ask your platform administrator to move the account to Trash. See Manage users list for the role-change and trash workflow.

3. Is the platform reliable enough for the business?

Open Backups. Count how many times in the quarter the backup ran on schedule versus missed. Any miss is worth a conversation with your platform administrator — not necessarily a crisis, but a data point. Check Audit Log for any Settings-level changes in the quarter that were not part of a planned initiative. Unplanned settings changes are the most common source of silent site regressions.

A quarter where the daily schedule held — every planned backup ran, with a manual restore point created before each launch — reads like this. Across the quarter there were 90 backups: 87 Automated, 3 Manual, and 0 Missed.

The number to read is the Missed count. Zero means the schedule held for the full quarter. Any count above zero is the data point you raise with your platform administrator.

A single miss is rarely a crisis on its own. But a pattern of misses — the same day of the week, the same time of month — points at something worth fixing before it matters. The other reliability read happens back in the Audit Log. Filter to Settings actions for the quarter and look for changes that were not part of a planned initiative. A notification preference your team agreed to change is fine. A billing detail, an email credential, or an integration that changed with no matching plan is the kind of silent change that causes a regression weeks later, long after anyone remembers making it. Two reliability signals, then: did the backups run, and did the settings stay where you expected.

See Create and restore backups for the backup schedule and the manual-backup workflow.

4. Is the plan tier still right for where the business is?

Go to Settings → Billing. Review your current plan limits — number of sites, users, storage. If you are consistently bumping against a limit, upgrade. If you provisioned capacity for growth that has not materialised, consider whether you are paying for a ceiling you do not need. This decision is yours. The technical execution is your platform administrator's.

Read each line as used against limit — the rows that sit close to their ceiling are the ones that drive the upgrade decision.

There are two ways a plan can stop fitting, and they pull in opposite directions. The first is bumping the ceiling: a row that reads at limit while you still have hires, sites, or storage growth ahead. That is the signal to upgrade — and to do it before the limit blocks the work, not in the middle of onboarding a new hire. If a row reads at limit and your near-term plan needs more, contact SGEN support to upgrade ahead of the need.

The second is paying for a ceiling you never reach. A row that sits far below its limit, quarter after quarter, with no growth earmarked for that headroom, is capacity you are paying for and not using. That is a cost worth questioning at renewal — not a reason to act mid-quarter, but a note for the next plan conversation. The decision in both directions is yours to make. The change itself — the upgrade, the right-size, the schedule — is your platform administrator's to execute once you have set the direction.

See Settings → Billing for the plan-tier review workflow.

Use this table to turn what you see into a next action:

Steps — quarterly review

The full quarterly review, as an ordered procedure.

The procedure, restated as imperative sub-steps:

The three founder KPIs you carry into that summary paragraph read like this at quarter-end:

What success looks like

You finish the 2-hour session with a one-paragraph summary you could paste into a board deck. You also finish with a clear, short list of decisions and follow-ups, each assigned to the right owner. Every founder question has an evidence-backed answer, not a feeling.

The summary reads in plain numbers: traffic up or down by a known percentage, a count of critical incidents, a backup success rate, and a one-line read on plan fit. The decisions read as ownership: a strategy ask for your marketing lead, a calendar reset for your content lead, a plan change routed to your platform administrator. Nothing in the output is a guess. Every line traces back to a screen you opened during the session.

A completed quarterly review looks like this:

What to do if it does not work

• You cannot open one of the five screens. You likely do not have read access to that area. Ask your platform administrator to grant Dashboard, Audit Log, Users, Backups, or Billing read access, then resume.
• The Dashboard does not show a 90-day range. Use the widest range your Dashboard offers and note the window in your summary. Or pull three monthly snapshots and compare them — the trend is what you are after, and three points draw a line. See Site Dashboard.
• The Audit Log looks empty for a stretch. Confirm your date filter is set to the full quarter before concluding there was a gap — a narrow filter can hide activity. If the gap is real, treat it as a question for the team, not a verdict.
• Backups shows a Missed count and you do not know why. Do not change the backup schedule yourself. Hand the count to your platform administrator with the dates — they can read why the job did not run and whether it needs a fix.
• Billing usage looks wrong. If a usage row does not match what you expect, contact SGEN support before acting. Do not change the plan on a number you cannot explain.
• The numbers do not match last quarter's summary. Confirm you are comparing the same date window — a quarter measured Jan-Mar will not line up with one measured Feb-Apr. Lock the window definition once and reuse it every quarter so the trend stays comparable.

Examples