Founder Resource · Outstep

My exact tool stack.
How I run Outstep .

You commented "tools" - so here it is. Every tool I use, how I set it up, the exact prompts I run, and how it all fits together. No fluff.

Muhammad Ashher
Muhammad Ashher Founder & CEO, Outstep · Top Rated Plus on Upwork
Three categories. Eight tools. This is the actual stack I use to serve 30+ clients with a lean team - not a curated list of things that sound impressive. Every section has a setup guide, real examples, and the exact prompts or workflows I run.
01 - AI Assistant
01
AI Assistant
Code · Content · Decisions · Meetings
GitHub Copilot
My primary coding environment. Inside Copilot I run two different Claude models depending on the phase - Opus for architecture, Sonnet for execution. The model you pick matters more than the IDE.
Plan Mode
Claude Opus - Architecture, data flow, module structure. Don't skip this step.
Execution
Claude Sonnet - Build module by module using the plan from Opus. Faster, cleaner, modular.
Setup Guide
1
Go to github.com/features/copilot and subscribe. The Individual plan covers everything you need to start.
2
Install the GitHub Copilot extension in VS Code (search "GitHub Copilot" in Extensions). Sign in with your GitHub account.
3
Open Copilot Chat (Ctrl+Shift+I / Cmd+Shift+I). At the top, click the model selector and switch to Claude Opus for planning sessions.
4
When ready to build, switch the model to Claude Sonnet in the same dropdown. This is your execution model - faster and enough for implementation.
5
Enable Agent Mode in Copilot settings for multi-file edits. This is what makes it feel like a real coding partner, not just autocomplete.
Exact Prompts I Use
Opus - Architecture Planning Prompt
I'm building [PROJECT NAME]. Here are the full requirements: [paste your full project spec / client brief] Generate a complete technical architecture plan including: - Module breakdown with file/folder structure - Data models and relationships - API design (endpoints, request/response shapes) - Key decisions and tradeoffs - Implementation order (what to build first) Do not write any code yet. Just the plan.
Sonnet - Module Execution Prompt
Here is the approved architecture plan: [paste Opus plan] We are now building Module [N]: [module name]. Spec for this module: [details] Requirements: - Follow the file structure from the plan exactly - Keep this module fully self-contained - Add JSDoc comments on all exported functions - Do not touch other modules yet Build it.
Code Review Prompt
Review this code for: 1. Security vulnerabilities 2. Performance issues 3. Edge cases not handled 4. Anything that would fail in production Be direct. If something is wrong, say it and show the fix.
Real Examples
Client Project - Loan Origination Platform
Started with Opus to design the full data model: borrowers, applications, documents, approvals. Got a complete folder structure and API spec. Then switched to Sonnet to build each module - auth, applications, document upload, admin dashboard - one at a time. Build time cut by ~40% vs. building without a plan first.
Client Project - Multi-Agent AI System
Used Opus to design the agent orchestration layer - how agents communicate, what tools each has access to, how state is managed. Sonnet then built each agent as a separate, self-contained module. Adding new agents later took under an hour because the architecture was clean from the start.
The Modular Workflow - How I Actually Use This
Plan first, always. Before opening a code file, spend 20–30 min with Opus getting a full technical plan. This eliminates the biggest time waster in software: building the wrong thing in the wrong structure.
One module per Copilot session. Open a fresh Sonnet session for each module. Keeps context clean and prevents the model from mixing up concerns across the codebase.
Always paste the plan. Every Sonnet session starts with the Opus plan. The model needs the full picture to write code that fits the architecture - not just the current file.
Review before moving on. Don't move to the next module until the current one is clean. Compounding bad code is the real risk - not slow progress.
Questions on the Opus → Sonnet workflow? Drop a comment on the post.
linkedin.com/in/muhammad-ashher →
Claude (claude.ai)
Separate from Copilot. This is my general-purpose AI for everything outside active coding - planning, writing, summarizing, client docs, decisions. It's open in a browser tab all day.
Setup Guide
1
Go to claude.ai and sign up. Pro plan gives you access to Opus and Sonnet - worth it.
2
Create Projects inside Claude for each client or recurring workflow. Projects keep your instructions and context persistent across chats - no re-explaining every time.
3
In each Project, write a custom system prompt : what the project is, the tech stack, the client's name, tone preferences, and any constraints.
4
Upload key documents to the Project - scope of work, requirements, previous conversations. Claude reads these in every session automatically.
Exact Prompts I Use
Client Proposal Generator
Write a project proposal for the following client request: [paste client's brief] Format: - Project Understanding (2 sentences - shows I read it) - Proposed Solution (what we'll build, not how) - Deliverables (bullet list, specific) - Timeline (realistic, phased) - Why Outstep (2–3 lines, no fluff) Tone: confident, direct, no buzzwords.
Call Transcript Summarizer
Here is the transcript from my client call: [paste transcript] Extract: 1. What the client actually wants (vs. what they said) 2. Key decisions made 3. Open questions / blockers 4. Action items with owner and deadline 5. Anything that might become a scope issue later Be direct. Flag anything that's a red flag.
Weekly Planning Prompt
Here are my active projects and their current status: [list each project + status] I have [X] hours of deep work available this week. Prioritize by: client deadline > revenue impact > complexity. Output a day-by-day plan. Monday to Saturday.
How I Use It Day-to-Day
📋
Document generation. Every client-facing doc - proposals, SOWs, project reports - starts as a Claude draft. Give it context, it generates structure, you edit the details. Faster than starting from scratch every time.
🧠
Decision making. When stuck on a technical or business decision, give Claude the full context and ask for a recommendation with reasoning. Forces you to articulate the problem clearly - which often reveals the answer anyway.
📝
Summarizing long things. Long email threads, docs, call transcripts - Claude condenses them into what you actually need in under 30 seconds.
Want the full list of prompts I use for client work? Comment "prompts" on the post.
linkedin.com/in/muhammad-ashher →
Gemini + NotebookLM
Free
Two Google tools for a very specific workflow: visuals and slide decks . Gemini for image generation. NotebookLM for turning a project document into a polished presentation in minutes. Both free, both massively underrated.
Setup Guide
1
Go to gemini.google.com - sign in with your Google account. Free tier is enough for image generation.
2
Go to notebooklm.google.com - sign in. Create a new Notebook for each project or topic area.
3
In NotebookLM, upload your source documents - PDF brief, Google Doc, website link, or pasted text. NotebookLM reads all of it and uses it as context for everything you ask.
4
Click Studio → Presentation to auto-generate a slide deck from your sources. NotebookLM structures it, adds talking points, and formats slides automatically.
5
Export to Google Slides, then adjust the design. The content is already done - you're just polishing the look.
Prompts & Instructions
Gemini - Image Generation for Posts
Create a clean, minimal graphic for a LinkedIn post about [topic]. Style: flat design, white background, muted professional colors. Include: a central visual metaphor for [concept]. No text in the image. Aspect ratio: 1:1 (square for LinkedIn).
NotebookLM - Slide Deck from Project Brief
[After uploading your project document, type in the chat:] Generate a client presentation that explains this project. Include: - Problem statement - Proposed solution - Key features - Technical approach (non-technical language) - Timeline and next steps Target audience: non-technical decision makers. One idea per slide. Max 8 slides. Keep it simple.
Real Example
Client Presentation - AI Operations Pack (14 Components)
Uploaded a 14-page technical specification document to NotebookLM. Asked it to generate a client-facing presentation. In under 3 minutes, it produced an 8-slide deck covering the problem, solution, system components, and rollout plan - all in plain language directly from the spec. Exported to Google Slides, restyled in 20 minutes, sent to client. Total time: ~30 minutes for a deck that would have taken 2–3 hours.
Doing a full post on the NotebookLM slide deck workflow. Follow to catch it.
Follow on LinkedIn →
Granola
Free
Meeting recorder that runs in the background on your Mac. Records the audio, transcribes it, and pulls out key points automatically. No bot joining the call. No one sees it. It just runs quietly and hands you everything after.
Setup Guide
1
Download Granola from granola.ai - Mac only currently. Install and sign in with Google.
2
Connect your Google Calendar . Granola detects your upcoming meetings and is ready to record when they start - no manual setup per meeting.
3
Grant microphone permissions. Granola records system audio + mic - it captures both sides of the call without joining as a visible participant.
4
After the call, Granola auto-generates a summary with key points, decisions, and action items. Edit or expand directly in the app.
5
Copy the transcript or notes and paste into Claude when you need to generate deliverables - proposals, follow-up emails, task lists - from the meeting content.
Post-Call Workflow with Claude
Granola + Claude - Follow-Up Generator
Here is the transcript from my client call: [paste Granola transcript] Generate: 1. A follow-up email (professional, under 150 words, confirms what was discussed and states next steps clearly) 2. A task list with: task description, owner, and deadline 3. Any scope concerns I should flag to the client now Tone: direct, no filler phrases.
How I Use It After Every Call
🎙
During the call: don't take notes. Be fully present. Granola handles it. You'll get more out of the conversation when you're not half-typing.
📄
Right after the call: Open Granola, skim the auto-summary, add any context it missed - tone, unspoken concerns, gut feelings about the client. Takes 3 minutes.
🤖
Generate deliverables: Paste the Granola transcript into Claude with the follow-up prompt above. You get a polished email and task list in under a minute.
💾
Archive it: Drop the meeting summary into the relevant WhatsApp project group or Trello card. Anyone on the team can reference what was discussed without asking you.
Granola + Claude is the most underrated combo for client work. Try it for one week.
granola.ai →
02 - Project Management
02
Project Management
Delivery · Team · Communication
Trello
Free
Every active client project has a Trello board. It's the single source of truth for what's done, what's in progress, and what's next. Simple, visual, and the whole team sees it at a glance.
Setup Guide - My Exact Board Structure
1
Go to trello.com - free tier is more than enough for teams under 10.
2
Create one Workspace called "Outstep" (or your company name). All client boards live inside it.
3
For each client project, create a new board with this 5-column structure - use it on every board without exception:

📋 Backlog - agreed on but not started
🔨 In Progress - actively being built right now
👀 In Review - built, waiting for review or testing
✅ Done - shipped and confirmed
⚠️ Blocked - waiting on client, third party, or a decision
4
Every card must have: a clear task name , the person assigned , and a due date . Cards without these go back to Backlog until they're complete.
5
Invite clients to their board as a viewer . This eliminates 80% of "what's the status?" messages - they can see everything in real time.
How We Keep It Clean - The Rules
📌
One task = one card. If a card has more than 3 checklist items, it's probably two tasks. Split it.
🔄
Update during standup. During the 10am standup, every team member moves their cards to the correct column. The board should always reflect reality - not what someone planned a week ago.
🚫
Nothing lives in "In Progress" for more than 3 days without a comment explaining why. Long-running tasks indicate something blocked or unclear - surface it early.
Real Example
Client Project - 14-Component AI System
When building the AI Operations Pack (14 components), each component got its own Trello card with a checklist of sub-tasks. The client could see every morning exactly how many components were done vs. in progress. Result: zero "what's the status?" messages for the entire project duration. Client trust went up, scope creep went down.
Want a copy of my Trello board template? Comment "trello" on the post.
linkedin.com/in/muhammad-ashher →
WhatsApp + Daily Standup
Free
Not Slack, not Notion, not Teams. If your team is under 10 people, you don't need a fancier tool - you need a better system. Here's the exact structure.
Setup Guide - Group Structure
1
Create one parent company group - I call mine "Discussions at Outstep." Company-wide updates, policy changes, team announcements only. Not project work.
2
Create a separate group for each client project. Include only the team members on that project. Name it clearly: "[Client Name] – [Project Name]".
3
Set a group description in each project group with: project overview, deadline, Trello board link, and point of contact. Anyone joining later has instant context.
4
Use pinned messages for important links - Trello board, staging URL, client drive folder. Findable without scrolling.
5
Turn on disappearing messages (90 days) in project groups. Old conversations clear automatically. No manual housekeeping.
The Daily Standup - Exact Format
Monday to Saturday · 10:00 AM · 20–30 minutes
Yesterday
What did you complete? (specific, not vague)
Today
What are you working on right now?
Blockers
Anything stopping you or that you need from someone else?
3 minutes per person, maximum. Standup is for alignment, not problem-solving. If an issue needs discussion, take it offline right after.
📲
Voice or video, not text. Async text standups fail - people paste a vague sentence and disappear. Being present for 20 minutes means genuine accountability.
📋
Update Trello during standup. As each person talks, they move their cards. By the time standup ends, the board reflects reality.
Why WhatsApp Beats Slack for Small Teams
The honest reason
Slack has channels, threads, statuses, integrations, huddles. For a 3-person team, this is overhead. Everyone is already checking WhatsApp 20 times a day. Meeting people where they already are removes every adoption barrier. Response times are faster, context is clearer (voice notes), and there's zero onboarding. When your team hits 15+ people across multiple time zones - then revisit Slack. Until then, this is faster.
Important: Keep client communication in email or a dedicated channel. Team WhatsApp groups are internal only. Never mix the two.
This standup format alone will save you hours a week. Try it Monday.
Connect on LinkedIn →
03 - Smart Calendar
03
Smart Calendar
Time Blocking · Focus · Scheduling
Google Calendar
Free
No fancy scheduling apps. Just Google Calendar used with intention. The difference between a productive week and a chaotic one is whether your calendar is built by you or filled by everyone else.
Setup Guide - My Weekly Block Structure
1
Create three separate calendars inside Google Calendar, colour-coded:
🟢 Deep Work (green) · 🔵 Client Calls (blue) · ⬜ Admin (grey). Everything goes into one of these three.
2
Block deep work time first , every week. I protect mornings - 9am to 12pm. Non-negotiable. No meetings, no calls, no interruptions. This is when the real work happens.
3
Designate specific days for client calls - keep calls to afternoons or specific days so they don't fragment the entire week. A fragmented day has no deep work.
4
Set one admin block per day - 30–45 minutes - for emails, proposals, invoices. Do all of it in this block, not scattered throughout the day.
5
Set your calendar's working hours (Settings → Working Hours) so no one can book you outside them. Sync your booking link (Calendly, Cal.com) to this calendar so available slots reflect reality.
The Time Blocking Philosophy
🧱
Protect the morning. The first 3 hours of the day are when your brain is sharpest. Client calls and admin can happen any time. Deep work cannot. Guard it like a meeting you can't cancel.
📵
Context switching is the enemy. Going from a client call → coding session → admin task → back - each switch costs 20+ minutes of recovery. Batching similar work into blocks eliminates this completely.
📅
Plan next week on Friday. Spend 15 minutes every Friday setting up next week's blocks. Move anything that didn't happen, add new priorities, protect deep work. You walk in Monday knowing exactly what you're doing.
🔒
Treat calendar blocks like meetings. If it's blocked, it happens. Don't cancel your own deep work block for something that "just came up" - that habit, compounded weekly, is what kills output.
My Typical Day Structure
Monday – Saturday (recurring blocks)
9:00 – 12:00 → Deep Work (coding, architecture, complex problem-solving)
10:00 – 10:30 → Daily standup (inside the deep work block - team-synced, fast)
12:00 – 1:00 → Lunch / buffer
1:00 – 3:30 → Client calls (specific days only - not every day)
3:30 – 4:00 → Admin block (emails, proposals, invoices)
4:00 – 5:30 → Deep Work Round 2 (review, documentation, next-day planning)
Saturday: Standup still happens at 10am. Half-day for overflow or high-priority items. Afternoons are off - protecting this is what makes the rest of the week sustainable.
Block your week before someone else does. This is the highest-leverage change on this list.
linkedin.com/in/muhammad-ashher →
Quick Reference
All 8 tools at a glance
GitHub Copilot
Coding - Opus for planning, Sonnet for execution
Claude (claude.ai)
Proposals, docs, planning, decisions
Gemini
Image generation for posts & assets
Free
NotebookLM
Slide decks from project documents
Free
Granola
Meeting recording & transcription
Free
Trello
Project tracking - 5-column board per client
Free
WhatsApp
Team comms + daily standup (Mon–Sat, 10am)
Free
Google Calendar
Time blocking - deep work, calls, admin
Free

Run this entire stack for free.

The only paid tools are GitHub Copilot and Claude. If you're early-stage and budget is tight, here's how to go fully free without losing much:

ChatGPT Free → replaces Claude for general tasks
GitHub Copilot Free tier → limited but usable for solo founders
Gemini Free → image generation, stays the same
NotebookLM → completely free, no catch
Granola Free tier → covers most use cases
Trello Free → more than enough under 10 people
WhatsApp → free. Already on your phone.
Google Calendar → free, always has been

Want to talk about building
AI systems for your business?

Outstep builds multi-agent AI systems, automation pipelines, and custom AI products for companies that want to actually move faster - not just talk about it.