Hub
Bring daily work into view.
Operational information and source documents come together in a review flow. A summary is a starting point, with the original evidence available for a closer look.
An internal-systems case study
A clearer view of day-to-day work.
An illustrative business workflow, using the tools Joel Spurling built for Growth Stack’s own operations.
Internal systems. Fictional business examples.
A workflow you can recognize
A question. A report. A next step.
A small service business starts the week with a document question, a website report to check, and a decision that needs research. Each needs a clear answer about what to do next.
I built these tools for my own operations at Growth Stack. This scenario shows how the same approach could apply to work in another business: bring the relevant information together, check what it supports, and choose a focused next action.
In this recording
- Hub: find what is due on a statement, then check the cited source before following up.
- SEO: check whether the website evidence supports a change or needs further investigation.
- Lab: define the scope and tools for a research question before starting.
Read the video transcript
Picture a small service business with three jobs waiting: a document question, a website report, and a decision that needs research. This illustrative workflow uses Growth Stack’s own operations.
Start with one question: what’s due on this statement? Hub brings the answer and its cited documents together. Check the source before acting.
Next, check the website evidence. SEO shows when information was collected, and how recent the underlying activity is. Missing data stays missing, so an unavailable comparison doesn’t become a misleading trend.
Lab supports local model processing. Web research and connected tools are explicit choices. My experience in regulated industries shapes those decisions.
Then choose one next action: check the source, investigate a reporting gap, or define a small change to test. The person running the business remains in control.
Need help with a workflow? Growth Stack offers project, hourly and contract support. Use the contact form to tell us what you’d like to improve.
Three tools, connected to the work.
SEO
Know what the report supports.
Reporting dates, source coverage and missing data sit alongside the numbers. An unavailable observation stays missing; a measured zero stays zero.
Lab
Give research a clear scope.
An investigation starts with a question, a research mode and a chosen set of tools. The result still needs review before it becomes a business action.
Where the work runs. How the answers are checked.
My background in healthcare and financial services shapes how I approach data handling, access and review. Those decisions belong in the design of a workflow, alongside what it needs to accomplish.
Local-first AI, with explicit tool choices.
Lab supports model processing on local infrastructure, with explicit choices about research modes and connected tools. Local processing is one part of the design; web tools and external services need their own data boundaries.
Compare models against the work.
My model-comparison work checks answers against the source material, including errors, omissions and unsupported claims. The useful question is which approach fits the task and what a person still needs to verify.
Start with a workflow in your business.
A customer follow-up that gets lost. A report that needs checking by hand. Information scattered across several tools.
We can agree on one problem and clear acceptance checks, implement a focused improvement, then walk through the result and hand over the documentation. The approach can use the tools you already have.