A shared reference for the tools and systems the AI Enablement team uses together, so our work stays connected and builds on itself.
When we use the same core tools, our dashboards, data pipelines, and creative assets connect naturally. This page captures the tools we've chosen together and the decisions still being worked through.
Wherever possible, the team's work connects to the same database, the same DAM, and the same task system. Confirmed tools are listed on the following slides. Open decisions are being finalized collaboratively in standup.
The goal is simply to make it easier for each of us to build on one another's work.
Claude Code and the API power our internal tooling and agents.
Home for our code, skills, configurations, and shared references.
Hosts our backend and primary database (app.sga3p.com).
System of record for operational data.
Where reporting and analytics data is served from.
Runs our scheduled and long-running workflows.
Our reporting layer, which reads from ClickHouse.
Standups and day-to-day team communication.
Decision lead: Sarah
Decision lead: Mike
Decision lead: Amy
Support and maintain the Postgres setup.
Railway hosts our backend and our Postgres database. Applications, ingestion workflows, and integrations all read and write here for operational data.
Analytics data flows onward into ClickHouse, and Power BI dashboards read from there rather than from Postgres directly.
Please check in with Scott or Dakota first. If Postgres doesn't fit a particular use case, we'll look at extending the shared setup together rather than running a parallel one.
This includes SQLite files, Supabase projects, Airtable bases, and similar temporary datastores.
We're selecting a single place to track work across the AI workstream. Once chosen, it will replace the mix of spreadsheets, Teams threads, and email chains currently in use.
Important: clear task ownership, status visibility, and the ability to link tasks to GitHub PRs and documents.
Helpful: Teams integration, support for recurring work, and a reasonable cost for around ten seats.
Options under consideration: ClickUp, Asana, Linear, Monday, Jira, GitHub Projects, and Microsoft Planner.
A single home for creative — brand materials, campaign files, social posts, logos, and templates. Having one source makes assets easier to find, reuse, and keep current.
Important: version history on assets, a clear folder structure by practice and brand, and permissions for internal versus agency access.
Helpful: previews for creative review, tagging and search, and integration with Canva or Adobe.
Options under consideration: Brandfolder, Bynder, Canva (team library), Frontify, SharePoint, Google Drive (shared drives), and Notion databases.
The central home for what the team needs to reference — SOPs, runbooks, onboarding materials, decisions, playbooks, and meeting notes.
GitHub is where our code, configurations, and shared references live. A few light practices help the team collaborate smoothly.
Sarah, Mike, and Amy will bring recommendations to standup this week. In the meantime, the rest of the team can build against the confirmed tools. As the open decisions close, this deck will be updated so we're all working from the same reference.