Questions buyers ask us, answered
Tasken sells premium custom software as a service. One question per page, and each page opens with the short answer.
What Tasken is
What does Tasken do?
Tasken sells premium custom software as a service. We design, build, host and maintain software around how your team works, with AI doing the repeat work inside it. It runs a workflow end to end, and your team signs in to check and approve the work. Each build is done once, then maintained monthly. The first step is your free build session.
Who is Tasken for, and who is it not for?
Tasken is for companies whose team does repeated manual work and wants to scale without hiring more people. Most are marketing teams, at agencies and in-house. You need no engineering team of your own. It is a weaker fit if you have no recurring manual work yet, or if you want a one-off build with nobody operating it.
What goes into Tasken's custom software?
The custom software we build runs a marketing team's workflow end to end on its own loops, and the team signs in to check, approve and rely on the work rather than operate it. It has a dashboard, a chat that reads the data and can act, and the workflows inside it, with approval gates, readable logs and a stop control. Scripts and automations are parts of it.
Is Tasken an SEO agency?
No. Tasken sells premium custom software as a service, mostly to marketing teams at agencies and in-house. SEO and GEO are where our expertise runs deepest, and where the method was proven first. Custom work covers recurring marketing workflows well beyond search: research, campaign operations, reporting, content operations, lead and account research, partner and creator discovery.
Can we build this ourselves with ChatGPT or Claude?
Often, yes. If someone on your team can build, monitor and maintain it, building it yourselves with ChatGPT or Claude may be the right route. We step in when the workflow needs integrations, controls and an owner after launch, because that is the work we keep doing every month once the build is finished.
Does Tasken fit agency delivery?
Yes. Agencies make up most of our client work, and we start with the workflows that usually add headcount: prospecting, screening, reporting and QA. Anything we host can be rebranded as yours, and you set your own client price. Every build starts with one delivery task in your free build session.
Custom builds
What happens on the free build session?
Your free build session is a thirty minute working session with Mudi. Bring one task your team still does by hand. We build the first working version of it live, in the tools you already use where we can, and it is yours to keep. If a product you already pay for can do the job, we will tell you instead.
Is the free build session the same as the full workflow audit?
No. The free build session covers one task, as a first version. The full workflow audit and architecture, the paid first stage, covers your whole operation. The session is thirty minutes with Mudi and costs nothing. The full workflow audit comes after it, and only if there is a fit.
What if the audit finds nothing worth building?
We tell you. If the work is not worth automating, or a product you already pay for can do it, you hear that instead of a proposal. No is a real answer, whether it comes in your free build session or in the full workflow audit.
How does a custom build run, step by step?
A custom build runs in six steps. Your free build session, thirty minutes on one task. The full workflow audit and architecture, the paid first stage. A UI review, where you see the interface before it is finished. A system review of the working tool, end to end. Delivery and training. Then Support & Upgrades, the monthly plan that keeps it running.
What does a custom build cost?
There is no public price, because an honest number needs the workflow map first. A custom build is priced per scope after the full workflow audit and architecture, and the price is fixed once the scope is agreed, with no hourly billing. The build is paid upfront. Support & Upgrades, the monthly plan that runs it after launch, is a separate fee.
How long does a custom build take?
A custom build averages three weeks from audit to live. That covers discovery and planning, then the build, then delivery and training. It is an average across builds, not a promise for yours: your own timeline is agreed in the scope, after the full workflow audit and architecture.
What is Support & Upgrades, and what happens if we stop it?
Support & Upgrades is the monthly plan after a custom build. We host it, watch it, fix it, and improve it with what we learn from other builds. New workflows and major features are quoted separately. It cancels any time, with no long contract, and if you stop it we move the system to your own infrastructure, free.
Do we need a technical team, and will it work with our tools?
No. We build around your current stack and handle the engineering, monitoring and maintenance ourselves. Your team gets custom software it signs in to, with approval controls where they are needed, wired into the tools it already uses: the CRM, the CMS, the ad platforms, even the sheet everyone lives in.
Where does our data go, and what can the tool do without us?
Each build gets only the tools and data its job needs, and that scope is written down before we build. Where a vendor is involved, you hold the account and the keys. We agree the approval level for every action, keep readable logs of every run, and give your team a stop control.
How involved does our team need to be?
We need one point person, access to the tools the workflow touches, and your team in two reviews, the UI review and the system review, so what we build matches how they work. Everything technical, the engineering, monitoring and maintenance, is ours. After launch, your team sets the rules and the approval level for each workflow.