It works where your work already is.
A Digital FTE does its job inside the systems your team runs today, with the permissions you grant and nothing more. No new dashboard, no migration, no rip-and-replace.
Finance & accounting
Ledgers, banking and payments the Finance FTE reconciles and reports from.
- QuickBooks
- Xero
- NetSuite
- Sage Intacct
- SAP
- Microsoft Dynamics 365
- Oracle ERP
- Zoho Books
- FreshBooks
- Wave
- Stripe
- PayPal
HR & recruiting
Applicant tracking and HR systems the Recruiter FTE screens and schedules in.
- Workday
- BambooHR
- Gusto
- ADP Workforce
- SAP SuccessFactors
- Zoho People
- Lever
- Greenhouse
- LinkedIn Talent
- Indeed
Customer support
Help desks and messaging channels the Support FTE resolves tickets in.
- Zendesk
- Intercom
- Freshdesk
- HelpScout
- Zoho Desk
- Salesforce Service Cloud
- ServiceNow
- HubSpot Service Hub
- Drift
- Crisp
- Twilio
- WhatsApp Business
Sales & CRM
CRMs and outreach tools the Sales Development FTE keeps clean and works from.
- Salesforce
- HubSpot
- Zoho CRM
- Pipedrive
- Freshsales
- Microsoft Dynamics 365 Sales
- Copper CRM
- Close.io
- Apollo.io
Ads & social
The channels the Performance Ads and Social Growth FTEs buy on and publish to.
- Meta (Facebook & Instagram)
- Google Ads
- YouTube
- TikTok
- X
- Mailchimp
- HubSpot Marketing
Publishing & search
Where the Search Visibility and Content FTEs publish, and how they measure.
- WordPress
- Shopify
- Next.js (via @ftes/publish-nextjs)
- Google Search Console
- GitHub
- GitLab
Productivity & documents
Where briefs, research sources and approvals live.
- Google Workspace
- Microsoft 365
- Slack
- Notion
- Asana
E-commerce
Storefronts the marketing FTEs publish to and measure against.
- Shopify
- WooCommerce
- Amazon Seller Central
A tool listed here means a Digital FTE can work in it. Which roles use which tools is on each role's page.
Granted by you. Scoped by design.
- 01
Per organization, per property
A connection belongs to your organization and, where it applies, to one website, store or ad account. One FTE's property never sees another's.
- 02
Permissions you choose
You grant the scopes a role needs and nothing more. Read-only where read-only is enough.
- 03
Revocable at any time
Disconnect from the workspace; the FTE loses access immediately and says so in its next brief.
- 04
Credentials encrypted at rest
API keys and tokens are encrypted before they are stored, with a key held separately from the data. Plain-text secrets never appear in responses or logs.
Three ways an approved article goes live.
The Search Visibility FTE writes and fact-checks; nothing publishes until you approve it. Where it lands depends on your stack.
WordPress
Approved articles publish through the WordPress API into the site you connect.
Shopify
Approved articles publish to your store's blog through the Shopify API.
Your own site
Install @ftes/publish-nextjs in your Next.js site and approved articles land there through a signed endpoint, with a cached-404 check so a bad publish is caught, not hidden.
Manage it from Claude or ChatGPT.
The shipped FTEs can be connected to Claude and ChatGPT through an MCP connector. From the assistant you already use, you can read the morning brief, list approvals, preview a publish and approve it. The connector link carries its own credential, is shown once, and can be rotated from the workspace.
See it on the Search Visibility FTEConnect the tools. Hire the role.
Sign up, grant the connections a role needs, and review its first proposals this week.