Scott Weir's 6-App Solutions Stack

Scott's been implementing enterprise solutions since before "solutions architect" became a job title everyone threw on their LinkedIn. Started in the trenches doing actual IT work, climbed into consulting, spent years figuring out why some tools stick and others get abandoned three weeks after launch.

What separates him from the typical consultant? He actually builds the systems himself instead of just writing recommendations that sit in a PDF forever. When he specs Coda for a client, he's the one setting up the first workspace and training the team on it.

By late 2024 he'd worked with around 80 companies, ranging from 10-person startups to Fortune 500 divisions. The pattern is always the same: they're drowning in tools that don't talk to each other, processes that exist only in someone's head, and Slack channels full of questions that get asked every week.

His philosophy boils down to boring consistency over clever complexity. The Scott Weir tools below aren't flashy. They're just what survives after watching dozens of implementations succeed or fail based on whether teams actually used them six months later.

Coda runs the show for every client engagement. Not Notion, not Monday, not some enterprise PM suite that costs $50 per seat. Coda.

Each client gets a custom workspace built from templates he's refined over years. Project roadmaps. Meeting notes with action items that auto-populate into task databases. Decision logs tracking who approved what and when. All living in one place instead of scattered across Google Docs, Trello boards, and email threads.

The killer feature for him? Packs. Coda's automation building blocks let him connect tables and create workflows without writing code. Client asks for a dashboard showing implementation progress? Twenty minutes in Coda versus three days building something custom.

He tried switching to Notion in 2022 when everyone was hyping it up. Lasted about six weeks before moving back. Notion's great for personal wikis. Coda handles actual project complexity better, especially when you need relational databases and conditional logic.

Linear handles the technical side when projects involve dev work. Issue tracking that doesn't feel like navigating Jira's nightmare interface. Integrates with GitHub so code commits automatically update tickets. Most importantly, engineers actually use it without complaining, which is basically a miracle.

Spark Mail replaced Gmail around 2020 and he hasn't looked back. Smart inbox automatically sorts urgent client requests from newsletter noise. Team features let his assistant handle scheduling without forwarding chains.

The send-later feature is clutch for managing client expectations. Answering emails at 11pm trains people to expect constant availability. Spark lets him write the response late but schedule it for 9am the next morning. Same result, healthier boundaries.

Snooze keeps the inbox clean without losing important follow-ups. Client says they'll have requirements ready Friday? Snooze the thread until Friday morning. No manual reminders needed, just surfaces when it's actually relevant.

Tried switching to Superhuman when they added team features in 2023. Couldn't justify the price difference when Spark handled 90% of the same use cases for way less money. Sometimes good enough actually is good enough.

Miro owns the discovery phase. Every new engagement starts with a workshop mapping current processes, identifying pain points, and sketching future state workflows. All happening on Miro's infinite canvas.

Templates speed things up massively. Journey mapping? Got a template. System architecture diagrams? Template. Brainstorming frameworks? Multiple templates refined over dozens of sessions. No need to rebuild the structure every time, just fill in client-specific details.

The sticky note feature shines during virtual workshops. Everyone throws ideas up simultaneously instead of waiting turns like in a regular video call. Then voting features help prioritize without endless discussion about what matters most.

Tried FigJam when Figma launched it. Nice tool, but Miro's templates library and third-party integrations are still deeper. Plus clients already have Miro accounts from other projects, so there's less onboarding friction.

Arc Browser changed how Scott organizes work across multiple clients. Each client gets a separate Space with its own tab setup, bookmarks, and login sessions. Switching between projects is just a keyboard shortcut instead of juggling Chrome profiles.

Vertical tabs keep 30+ resources visible without the horizontal tab bar becoming useless. Documentation, Coda workspaces, Linear boards, client Slack channels, all accessible in the sidebar. Split view lets him reference specs while building solutions without constant window switching.

Raycast ties everything together as his command palette for the entire computer. Launching apps, searching Coda docs, creating Linear issues, converting timezones for client calls across three continents. All without touching the mouse.

Custom scripts automate the boring stuff. Weekly client reports get generated from Coda data with one Raycast command. Meeting prep pulls up the right tabs and documents automatically. Saves maybe 20 minutes daily, which compounds to real time savings over a year.

Tried switching back to Chrome in mid-2024 when Arc had some stability issues. Lasted three days before the lack of Spaces drove him back. Once you organize work that way, going back to traditional browser tabs feels like amateur hour.