Internal GTM apps are custom tools for your sales and marketing team. An AE can open a meeting brief with the last conversation, recent company news, and questions to ask. An SDR can see which lead needs a reply and why.
Deepline gives your app access to sales data and workflows. You decide which accounts matter, how to qualify a lead, and what your reps should see. Your team or coding agent can build internal tools around those decisions.
| Internal tool | What the rep gets | What it needs |
|---|---|---|
| Sales meeting prep | An agenda, previous commitments, and questions for the call | Calendar, attendees, CRM notes, and account research |
| Sales signals | A reason to contact an account, with a source to check | Company changes, your target customer criteria, and existing contacts |
| Lead qualification | A next step for each lead and a reason for it | Form response, company data, qualification rules, and account owner |
| Account planning | Customer goals, people involved, and next actions | Call notes, CRM records, owners, and due dates |
Start with the task your reps repeat most. Watch someone do it. The time they spend hunting for information tells you what the app needs to bring together.
Try the sales signals and meeting prep workflows
We turned two customer workflow patterns into starting points you can adapt. The examples use fictional data and contain no customer names or private settings. A Play is a saved workflow in Deepline.
Sales signals: find a reason to reach out
The sales signals workflow takes company updates you supply, filters out old or repeated events, and compares them with what you sell. It returns a possible reason to reach out, a suggested question, and the source behind it.
A new office gives an office equipment seller a useful question: who is handling the setup? It does not tell you whether the company has already chosen a supplier. Set your rules around what makes a change relevant to your product.
Sales meeting prep: know what to ask
The sales meeting prep workflow takes a scheduled meeting, its attendees, CRM notes, and account research. It returns a draft agenda, questions to ask, and gaps to fill before the call.
Both workflows use the data you give them. They do not yet connect to your CRM or calendar. Open either one and tell your agent:
Make this work for my use case. Ask what we sell and how our reps work. Connect our data, then show me a sample before you schedule it.
For the code and test data, download the sales signals source and sample input, or the meeting prep source and sample input. These versions produce drafts for review. Your agent can add CRM updates or delivery when you are ready.
What should you buy, and what should you build?
Buy the infrastructure your team needs: a CRM, access to data, and somewhere to run the workflows. Build the parts that depend on how you sell.
Your qualification rules, account priorities, and meeting questions belong to your business. Put those rules in a tool your reps can use. A Slack message or a CRM view may be enough to start.
Deepline handles the data and saved workflows. The same Play can run from your app or an agent through the API, SDK, or CLI. You can inspect what happened on each run and update the workflow as your process changes. Your team owns the interface, who can access it, and who maintains it. See how Plays work.
Internal tools examples from Deepline customers
Attention: match the buyer to the right AE
Attention combines CRM records, sales conversations, and enrichment data to study which AE is a good fit for a buyer. It uses the result in its booking flow. Its account based marketing system also tracks which people know the product and where the team lacks contacts in the buying group.
Deepline supplies company, technology, and public profile data into Attention's Snowflake database. Attention builds the rules that use it. Read Attention's story.
Adapt: give reps a shared sales workflow
Adapt moved workflows that individual reps had built into a shared library of Deepline Plays. Its sales signals workflow checks whether an account fits, finds contact details, adds HubSpot context, and sends the result to Slack.
A rep gets the information in a tool they already use. The team can fix the shared workflow once instead of maintaining a separate version for each person. Read Adapt's story.
More internal apps worth seeing
These public demos show what people built. They are separate from the Deepline customer examples above.
- Profound: Nick Lafferty built a Google Ads reviewer that sends suggestions to Slack for approval. He also showed social post metrics beside HubSpot leads. Watch the demo.
- WorkOS: Jack Perales showed account and contact lookup that teammates and agents can use, along with event workflows. Watch the demo.
- Go Nimbly: Jen Igartua built an event app for guest nominations, approvals, attendee notes, and follow up. Salesforce keeps the records. Watch the redacted demo.
Noah Adelstein's article on Edgar Sze at Profound describes how Edgar watched reps prepare calls and follow up before deciding what to automate. He used Dust as the shared interface and built the data connections and deck workflows around it. The article was produced in partnership with Dust.
How to build your first internal sales tool
Choose one job and one rep who does it often. For meeting prep, start with a real upcoming call. Ask the rep what they need to know, where they find it, and what they usually miss.
Build a draft brief from those sources. Show the last conversation, what has changed, and what to ask next. Put a link and date beside each finding so the rep can check it. If the research finds a job posting that mentions SQL, show that fact. It does not tell you which database the company uses or whether it needs your product.
Let the rep correct the draft. Keep their corrections when you refresh the research. If a source is missing or two sources disagree, show the gap. Do not turn missing information into a confident answer.
Your developer should keep API keys on the server and check which accounts each user may view. Add approval before the app sends a message or changes a CRM record. These checks are part of building an app people can trust.
Use the app on a few real tasks. Compare the time spent, mistakes corrected, and next steps completed with the old process. Keep improving the part that gets used.
Start with the account research template, lead qualification checklist, or sales account planning template. The SDK quickstart shows your developer how to run a Play from an app.