Running a portfolio of several SaaS products alongside consulting mandates sounds like a recipe for overload. It works nonetheless, not through more hours but through a structure that decides what gets attention in a given week at all. This article describes the principles Innopulse works by. It is not a productivity guide but a description of trade-offs.
The premise: attention is the bottleneck
Time can be planned; attention cannot be divided at will. Jumping between a client mandate, three products and sales in one day gets a lot done and achieves little. The most important decision in a weekly rhythm is therefore not how many hours you work but how many different contexts you allow per day. Our rule: one main context per day or half-day wherever possible.
Mandates take priority, products get windows
Consulting mandates have fixed dates, dependencies and people waiting. They therefore get the days on which they happen in full. Product work gets its own protected blocks: one for development, one for content and growth, one for operations. Pushing products into the gaps between mandate meetings means doing only maintenance there, never progress.
What must run without attention
A portfolio can only be run if normal operation needs no daily care. That is an architectural decision, not a matter of discipline:
- One stack for all products: the same base of Next.js, Supabase and Stripe, the same patterns for authentication, tenant isolation and billing. A problem solved once is solved for every product.
- Automated checks: builds, tests and SEO audits run automatically before every release; a batch with errors does not go live.
- Monitoring rather than checking: errors, failed payments and anomalies report themselves instead of having to be found; more under observability.
- Reusable content: programmatic SEO with real data instead of individual campaigns rebuilt each time.
The weekly structure
The week starts with a short overview: which mandate dates are fixed, which product gets this week’s development block, which metrics have moved? From that comes a list of at most three outcomes for the week, not thirty tasks. Mid-week hold the mandate days and the protected product blocks. Before the new cycle, a review: what was shipped, what was not, and why? The review is the most important ritual, because it shows whether the rhythm holds or only feels as if it works.
What is deliberately left undone
Running a portfolio means constantly deciding what will not happen. Not every product gets attention every week; some run in operating mode for weeks while one is actively developed. Not every feature request is built. Not every channel is served. The skill is that leaving something is a decision, not an omission — and that it is documented so it can be picked up again. The same discipline applies to deciding which tools to build and which to buy.
AI as leverage, not replacement
AI tools shorten many steps, in code, in structuring content, in research. But they shift work more than they abolish it: what is produced faster must be checked. What has worked is using AI where the result can be checked automatically, through tests, type checking or audits, and taking personal responsibility for every statement in content with legal or professional weight.
How to tell the rhythm is breaking
When product blocks are regularly sacrificed for urgent small things. When the weekly review is skipped for lack of time. When customers wait for answers that used to come the same day. And when metrics such as churn worsen without anyone noticing. Then the answer is not more effort but fewer simultaneous workstreams: put a product into operating mode, close a mandate cleanly, drop an initiative.
What this means for clients
Clients working with Innopulse benefit from our own products supplying the reference architecture. Patterns that hold up in several products in production go into client projects, and mistakes we have made ourselves are not repeated on the client’s budget. Engineering detail on that stack is in our article on the Next.js 15 App Router in production; for a specific project, book an initial conversation.