An automated weekly business report sounds like something only companies with a data team get. For a solo founder, the “report” is usually Monday morning: open Stripe, open Google Analytics, open YouTube Studio, open the CRM, copy a few numbers into a doc, and try to remember what last week looked like. It takes 30 to 45 minutes when it goes well. When the week is busy, it does not happen at all, and that is exactly the week you needed it.
This post shows how to build that report once, as a Flow in Vexlynk, so it lands on your board every week without you assembling it. It also covers the one condition you need to know about before you rely on it: where your board lives decides whether the report can run while your computer is off.
What should a weekly business report actually include?
Less than you think. A weekly report for a one-person business is not a dashboard. It answers three questions:
- What came in? Revenue, new customers, bookings, leads. Whatever money or pipeline means in your business.
- What moved? Traffic, audience, the content that performed, the deals that changed stage.
- What needs attention this week? The one or two things that look off and deserve a closer look.
If your report answers those three in a few short paragraphs, it is doing its job. Anything longer tends to get skimmed and then ignored, which defeats the point of automating it.
How do you build an automated weekly business report in Vexlynk?
A Flow is Vexlynk’s automation. It reads your source cards, thinks about what it read, and puts the result on your board on a schedule you set. Where you might ask the agent a question once, a Flow does the same job again and again without being asked.
Step 1: Give it something to read
A Flow works on source cards, the live data already arriving on your board. So connect the sources your report should cover first. A common setup for a small online business: Stripe for revenue, Google Analytics for traffic, YouTube for the channel, and HubSpot or Calendly for pipeline and bookings. The full list is on the sources page, and Connecting Sources walks through each one.
A board with no sources has nothing to automate. That is not a limitation you will hit for long, but it is the first thing to check.
Step 2: Build the Flow
- Open Flows in the rail and go to the Builder.
- Choose what it reads: select the source cards you just placed.
- Say what it should do with them. This is where you describe the report in plain words.
- Set the schedule: weekly, on the day and time you want it waiting for you. Monday at 8:00 is a good default.
- Save it.
From then on it runs on its own and drops its result on your board as a card.
Step 3: Write an instruction that gets a useful report
The instruction is the difference between a report you read and one you scroll past. Be specific about the shape you want. For example:
“Write my weekly report. Three short sections: what came in (from the Stripe card), what moved (from Google Analytics and YouTube), and the one thing that looks off and is worth my attention this week. Use only what the cards show. Keep it under 200 words.”
Two habits help. Name the cards you care about, so the report does not wander. And write the instruction around what your cards actually hold: a Flow reads your source cards, so if a number is not on any of them, the report cannot know it. If you want refunds in the report, make sure the card you connected shows refunds.
Does the report run when my computer is off?
This is the part to get right before you depend on it.
A Flow runs without the app open only when the board is in the cloud. That means one of two setups:
- You work in the web workspace at workspace.vexlynk.app, where your boards already live in the cloud.
- You work in the desktop app with Sync turned on. Sync is opt-in, off by default, and a Plus and Pro feature (see plans).
If you use the desktop app with Sync off, your board lives only on your own computer. That is the private, local-first setup, and many people choose it on purpose. The trade-off is that nothing in the cloud can reach that board, so the Flow can only run while Vexlynk is open on your machine.
One more fact worth knowing: Flows that run in the cloud use Vexlynk’s hosted AI. If you have connected your own AI key for chat, a cloud Flow still runs on Vexlynk’s AI, not your key.
How do I know the report actually ran?
Open Flows and check Run history. It shows what happened each time the Flow fired, and it answers the first question that matters when a report is missing: did the run happen at all? A Flow that never fired and a Flow that fired and produced little are different problems. The first is usually about the schedule or where the board lives. The second is usually about the sources or the instruction.
The Library lists every Flow you have made. Open one to edit the instruction or schedule. If a Flow gets noisy for a week, you can disable it without deleting it, then turn it back on later.
Flow, Vlynk, or just asking the agent?
Three things in Vexlynk look at your data, and it is easy to reach for the wrong one:
- The agent answers when you ask, in conversation. Use it for a one-off: “how did last week compare?”
- A Vlynk is a standing analysis of your whole board, written as a card with findings cited to the cards they came from. You can run it on demand or set it to run daily or weekly. Financial Control, for example, reads budget against spend and your cash position.
- A Flow places a result on your board, on a schedule you set, from the source cards you chose and the instruction you wrote.
For a weekly report in your own words, built from the sources you pick, a Flow is the right tool. If you would rather have a fixed, published analysis with every finding cited, look at the Vlynks instead. Many people end up using both.
Isn’t this what automation tools already do?
Partly, but the job is different. App-to-app automation is about moving data: a new form entry becomes a CRM row, a payment triggers a message. A Flow does not move your data anywhere. It reads what is already on your board and writes a result next to it, so the report sits beside the numbers it came from. We wrote up the difference in more detail in Vexlynk vs Zapier.
When Vexlynk is not the right fit
- You need the report in someone’s inbox. A Flow puts its result on your board. If a client or investor expects a PDF by email every Friday, a dedicated reporting tool is a better fit.
- You need branded client reporting. Agencies sending white-labeled reports to many clients need software built for that.
- You want a fully offline setup and an unattended report. You can have one or the other. With Sync off, the Flow runs only while the app is open.
- Your data is not in a connected source. If the numbers live only in your head or in a tool Vexlynk does not connect to, a Flow has nothing to read.
If none of those apply, the setup takes a few minutes and pays you back every Monday. Try Vexlynk in your browser, where your board already lives in the cloud and Flows can run without you, or download the desktop app. The Flows docs cover every step, and the features page lists what ships today.
Frequently asked questions
Can the report run every week on a specific day?
Yes. When you build the Flow you set how often it runs. For a weekly report, choose a weekly schedule and the day and time you want the result waiting on your board.
Does an automated weekly business report in Vexlynk work with the app closed?
Only when the board is in the cloud: in the web workspace, or in the desktop app with Sync turned on. With Sync off, the board exists only on your computer, so the Flow runs while Vexlynk is open.
What data can the Flow read?
The source cards you choose when you build it, such as Stripe, Google Analytics, YouTube or HubSpot. Connect at least one source before you start. A Flow cannot report on numbers that are not on a card.
What if the report did not show up?
Check Run history in Flows. It tells you whether the run happened. If it never fired, check the schedule and whether the board is in the cloud. If it fired but the result is thin, check the source cards and sharpen the instruction.
Can I pause it for a week?
Yes. Open the Flow from the Library and disable it. It stops running but is not deleted, so you can turn it back on whenever you want.
Vexlynk
Vexlynk Team