NewOur sales playbook: 400+ pages, free to downloadDownload
App · Custom AI apps

Apps built for your team, not prompts.

Start with our standard apps, pick from more than 100 in the app store, or describe a new one in the chat. Taskbase builds it as code in 5 to 10 minutes, and you can change it at any time.

Monday 09:00 · your app “Weekly licence buyers”

4 companies bought a licence last week and fit your ICP

Territory DACH · ICP from your playbook · contacts with contact data

Corvin Software240 employees · Zurich · 5 licences bought

  • Nina BaumannHead of Salesn.baumann@corvin.example
  • Reto AebiVP Operationsr.aebi@corvin.example
  • Eva MorettiSales Directore.moretti@corvin.example

Lumeo Systems410 employees · Basel · 12 licences bought

  • David RothChief Revenue Officerd.roth@lumeo.example
  • Sara LindqvistHead of Enablements.lindqvist@lumeo.example
  • Jonas FreiSales Managerj.frei@lumeo.example

2 more companies

Add all to HubSpotDraft the emails

The result of an app, every Monday at 9:00. Companies, people and contact data are fictional.

100+apps in the Taskbase app store, ready to choose for your use cases
5 to 10 minto build a new app, by describing what you want
1 h+saved per rep and week by one example app: the weekly list of licence buyers

From a sentence to an app that runs

  1. 1Ask in your TaskbaseSay what you want, how often and for whom, in plain words.
  2. 2It checks the app storeIf an app for it already exists, Taskbase shows it and you can use it right away.
  3. 3Or the app builder builds itIf nothing fits, the app builder codes a new app in 5 to 10 minutes, asking only for what it is missing.
  4. 4Change it, build moreAdapt any app by chat whenever you want, and build as many as you need.

Code, not text

An app is code, not a prompt

A text skill is a document the model has to read and re-interpret on every run. A Taskbase app is coded: fixed sources, fixed steps and a finished view. The model is used where judgement is needed.

  1. 01

    The same result on every run

    What must always happen the same way is fixed in code. Reps get the same structure every time and know where to look.

  2. 02

    Reviewed before anyone uses it

    Taskbase reviews the code of every new app: does it do the job, how good is the result, how efficiently does it run and how well does it fit the use case.

  3. 03

    Seen and measured

    You see whether people open an app and how much time it saves. A text skill stays invisible: you do not know whether anyone read it.

Skill or app

What a text skill looks like, and what a Taskbase app looks like

A general model such as Claude gives you skills: text it interprets again on every run. Our first version used skills too, and had exactly these problems. Now every use case in Taskbase is an app: coded functions, connected sources and a finished view.

A text skill

Skills / Meeting briefing

Catalogue

Description

Before every customer meeting, give the rep a briefing. Look up the company, read the last calls and the CRM record, and decide what matters. Keep it short unless the rep asks for more.

Purpose

Give the rep a personal read, not a summary of everything. It answers three questions in plain language:

  1. Who is in the meeting, and what do they care about?
  2. What was agreed last time, and what is still open?
  3. What is the one thing to get out of this meeting?

Rules

  • Subject is always the calling user.
  • Never list other reps or the team.
  • Resolve the org at runtime, never a hardcoded domain.
A Taskbase app

Meeting briefing

SharedBuildOpen view
OverviewTemplate
Slug
meeting-briefing
Data path
views/meeting-briefing.json
Endpoint
meeting-briefing-metrics
  • Published to other agents
  • Pinned for everyone

Fixed sources, fixed steps, one finished view

// the same sources, in the same order, every run
const account = await crm.account(meeting.accountId);
const calls = await recordings.last(account, { n: 2 });
const rules = await playbook.section('discovery');

// the model only judges what matters here
const focus = await model.pick({ account, calls, rules });

return render({ who: account.contacts, history: calls, open: focus });

The same briefing as a text skill and as a Taskbase app. Content is fictional.

  • Sources, steps and layout are fixed in code, so the output does not drift.
  • The model is used only where judgement on this account or this call is needed.
  • Taskbase reviews the code and adapts the app when the use case changes.

Standard apps and the app store

Start with ours, change anything, build more

Taskbase comes with standard apps for the common use cases, and an app store with more than 100 apps to choose from. Take an app as it is, or individualise it: you can change any app at any point in time, and build more.

Top cold call list of the day

Update list
1
Marc DuboisRegional Sales Director · Alpenwerk Security
HotReady for outreachPartner referral3,800 employeesGeneva, Switzerland

Alpenwerk Security is a Swiss cybersecurity provider offering managed security services, advisory and technology consulting.

Score: 75

Account fit 0Role fit +15Lead status +10Partner referral +50

Why now: recommended directly by a partner contact, and opened your lemlist sequence three times this week.

Open in HubSpot
2
Lena HartmannHead of Sales & Marketing · Brantec IT
HotReady for outreachPartner referral650 employeesBaden, Switzerland

Brantec IT provides managed services, SAP consulting, IT security and cloud solutions across industries in Switzerland.

Score: 75

Account fit 0Role fit +15Lead status +10Partner referral +50

Why now: recommended directly by a partner contact, and replied to your last lemlist email.

Open in HubSpot

A standard app: the prioritised call list. Names and companies are fictional.

  • Ask for something in your own Taskbase and an app already exists? Taskbase shows it, and you use that one.
  • Nothing fits? The app builder builds a completely new app for you.
  • Every app, standard or your own, can be changed later by telling Taskbase.

Build it

Say what you want, and the app exists

A client with a product-led motion had no easy way to see who had bought a licence on their own. Reps would have had to dig through the CRM, find the accounts big enough to matter, then search for people and contact data. Now a rep describes the job once, and every Monday at 9:00 gets the companies that bought a licence last week and fit the ICP, with three contacts each and their contact data.

Every Monday at 9:00, send me everyone in my territory who bought a licence last week and fits our ICP. Find three contacts per company, with contact data.

Got it. Your licences sit in your own product database. Shall I read them through its MCP?

Yes, use the MCP. My territory is DACH.

Done, built in 7 minutes. I’ll run it every Monday at 09:00 and post the result here. This week 4 companies would qualify.

New appWeekly licence buyers

Mondays 09:00Territory: DACHICP from your playbookSource: your product database

Make it Tuesdays, and only companies with more than 200 employees.

Updated. Next run: Tuesday 09:00, companies over 200 employees.

Describing an app, and changing it. Company, territory and numbers are fictional.

  • The app is built in 5 to 10 minutes, by talking to Taskbase. It saves a rep at least an hour a week.
  • It reads your own tool when that tool has an API or an MCP, and you allow it.
  • Change it any time by telling Taskbase: another day, another filter, another channel.

Where it runs and what it reads

Your tools, your channel

An app reads your CRM and, through an API or an MCP, your own tools, finds contacts with the data tools you connect, and delivers in the chat your reps already use.

  • HubSpot
  • Salesforce
  • Prospeo
  • Clay
  • FullEnrich
  • lemlist
  • LinkedIn
  • Slack
  • Microsoft Teams
  • Google Chat
  • … and many more

Tell us the app you wish you had

We build it with you in the meeting and show it running.