Most authors do not wake up thinking, "I would love another dashboard."
They wake up thinking about a launch that is approaching too quickly, a newsletter that needs writing, an ad that is spending money without making its case, a Kindle Countdown Deal they still do not fully understand, or a book page that probably needs updating before the next promotion goes live.
The work is rarely one neat task. It is a collection of small questions.
How should I launch this book?
Why is this Facebook ad not converting?
Which KDP categories should I choose?
What should go in the next newsletter?
Which promotion should I try next?
Independent authors have always had to answer questions like these. What has changed is where many of those questions now begin.
Increasingly, they begin in a conversation.
An author opens ChatGPT or Claude and starts thinking out loud. They explain the book, the audience, the price, the promotion, the last thing they tried, and the thing they are worried about trying next. They ask for options. They push back. They ask for a simpler version. They compare strategies. They use the conversation as a thinking surface.
That does not make the assistant the whole workflow. It simply means the conversation has become one of the places where the work starts to take shape.
And once you notice that, a question follows.
If authors are already using AI assistants to think through publishing and marketing problems, why should the software they use sit outside that conversation?
The quiet shift in author workflows
This is not a prediction about some distant future.
It is a fairly ordinary observation about how many authors are already working.
They are not necessarily thinking of themselves as technical users. They are not studying protocols or diagrams. They are not trying to redesign their process around software. They are just asking practical questions in the place that feels easiest to ask them.
"I have a mystery novella going on sale next week. What should I do first?"
"Here is my ad copy. Why might readers ignore it?"
"I have three books in a series. How should I structure a newsletter sequence?"
"My Amazon page gets traffic, but sales are flat. What should I look at?"
"How do Kindle Countdown Deals actually work?"
That kind of question used to be split across search results, blog posts, Facebook groups, YouTube videos, course notes, old bookmarks, and half-remembered advice from other authors.
Now, a growing number of authors put the question into an assistant first.
Not because the assistant is always right. Not because it replaces judgment. Not because publishing suddenly became easy.
Because a conversation is a natural shape for uncertainty.
When you are unsure what to do next, a blank search box can feel strangely demanding. You have to know what to search for before you know what you need. A conversation is more forgiving. You can begin messily. You can say, "Here is the situation," and work from there.
That matters for author software.
For years, most tools have assumed that the dashboard is the center of the user's attention. The author signs in, clicks through the navigation, finds the right page, adjusts the right setting, checks the right report, copies the right link, then leaves.
Sometimes that is exactly right. Dashboards are useful. Tables are useful. Charts are useful. Forms are useful. A well-designed interface can make complicated information understandable at a glance.
But a dashboard is not always where the author's mind is.
Sometimes the author's mind is in the middle of a question.
The cost of leaving the conversation
Context switching sounds like a productivity phrase, but authors know the feeling without needing the terminology.
You are in the middle of planning a newsletter and you realise you need the campaign link for the sale.
You open the dashboard.
You find the book.
You check which edition is linked.
You wonder whether the paperback target is still correct.
You open another page.
You copy the campaign URL.
You return to the newsletter, but the sentence you were holding in your head has gone.
None of those steps are dramatic. That is almost the problem. They are small enough to tolerate, which means they accumulate quietly.
The same thing happens when an author is asking an assistant for help.
They might be working through a launch plan in ChatGPT and suddenly need to know which campaigns already exist for a book. They might be discussing ad performance in Claude and need to check whether Facebook clicks are actually reaching a retailer. They might be comparing newsletter ideas and need to create a clean link for a subscriber-only promotion.
Each task is simple.
Check campaign performance.
Create a campaign link.
Update an author profile.
Check analytics.
Confirm which edition is linked somewhere.
Look up which retailer targets are missing.
But every switch has a cost. The author leaves the conversation, finds the application, searches for the relevant record, performs the task, copies the result, then returns and tries to re-enter the same mental space.
Software often treats that as normal.
I think it is worth questioning.
If the author is already thinking through the promotion in an assistant, why should book marketing data require a separate detour every time?
Why should the author have to leave the place where the decision is being made in order to retrieve the information needed to make it?
Conversations are becoming another interface
This does not mean dashboards are going away.
They should not.
There are plenty of moments when a visual interface is the best tool for the job. You may want to scan a list of campaigns, compare charts, edit a book page carefully, review every retailer option, or work through a form without ambiguity. Good software still needs clear screens, sensible navigation, and predictable controls.
But conversation is becoming another interface.
Not the only interface.
Another one.
That distinction matters.
When people talk about AI and software, the discussion often becomes too grand too quickly.
That is not how most useful changes actually arrive. More often, a new interface becomes useful for a particular kind of work, and people gradually work out which tasks belong there.
AI assistants are becoming useful for a certain kind of author work: questions, planning, interpretation, comparison, and small operational tasks that naturally sit inside a larger conversation.
An author might ask:
Which of my recent campaigns seems most promising for another push?
That question is not just a request for a chart. It needs context. What book are we talking about? What promotion ran? Which clicks mattered? Which countries responded? Was the goal visibility, sales-page traffic, newsletter growth, or testing a new angle?
A dashboard can show the underlying numbers. A conversation can help the author reason about them.
The best answer is not to pick one and discard the other.
The best answer is to let them work together.
Why we built Tutarium this way
Tutarium is built around practical book marketing work: public book pages, campaign links, author profiles, regional store routing, edition management, and analytics that show which promotions send readers toward stores.
Those things still need a proper product interface.
Authors should be able to sign in, review their books, edit pages, create campaigns, and inspect analytics without having to phrase everything as a question.
But we also know that more and more of the thinking around those tasks now happens in ChatGPT, Claude, and other assistants.
So we built Tutarium to meet authors there too.
That means an author can be in the middle of a conversation about a launch and ask the assistant to help with Tutarium data or actions, where access has been connected and approved by the author. They can ask which books are missing retailer targets. They can create a campaign link for an upcoming newsletter. They can check which campaign performed best. They can ask whether an author profile has the right books visible. They can use their own saved book marketing information as context for the conversation they are already having.
The author does not need to care about the machinery underneath.
They do not need to understand OAuth.
They do not need to know what an API is.
They do not need to study MCP beyond the simple fact that it lets compatible assistants connect to tools like Tutarium.
The important point is choice.
Tutarium works with ChatGPT, Claude, and custom AI assistants using MCP, so authors can use whichever assistant already fits their habits. Some people prefer ChatGPT. Some prefer Claude. Some work with a custom setup because their publishing process has grown more specific over time.
The product should not punish that preference.
If the author's working space is a conversation, Tutarium should be available there. If the author's working space is the dashboard, Tutarium should be comfortable there too.
The philosophy is simple:
Technology should adapt to people, not force people to adapt to technology.
That sounds obvious until you look at how much software quietly asks people to rearrange their lives around it.
Small tasks matter because they happen often
One trap in product design is assuming that only large tasks deserve attention.
Large tasks are easy to notice. Setting up a book page matters. Building an author profile matters. Planning a launch matters. Running a campaign matters.
But small repeated tasks shape how a product feels.
Can I quickly find the right link?
Can I tell whether the newsletter did anything?
Can I create a clean campaign URL without breaking my train of thought?
Can I ask a follow-up question without rebuilding all the context from memory?
Authors spend a lot of time in the gaps between larger projects. The book is written, but the page needs tidying. The launch is planned, but the newsletter link is missing. The sale is live, but the results are unclear. The ad is running, but the next decision depends on whether readers are clicking through.
Those are not glamorous moments.
They are the texture of the work.
If software adds friction in those moments, the author feels it. Maybe not as one obvious failure, but as a slow drain. A little more tab switching. A little more copying and pasting. A little more trying to remember whether the link in the Facebook post was the regular book link or the campaign link for the February sale.
When a tool can answer those small questions inside the conversation where the author is already thinking, it removes more friction than it might appear to remove.
It lets the author stay with the problem.
Author-first does not mean dashboard-first
It is easy for software companies to mistake usage patterns for loyalty. If people spend a lot of time inside a dashboard, the company may conclude that the dashboard is central to the user's work.
Sometimes that is true. Other times, people spend time there because the product gives them no other choice.
For authors, the center of the work is not a dashboard. It is the book, the reader, the launch, the newsletter, the next experiment, the decision about where to spend another hour.
The software is there to support that work.
That is why we are cautious about treating AI integrations as a shiny separate feature. The point is not to make authors admire the integration. The point is to make the product feel less like a place they must remember to visit and more like something available when it is useful.
Sometimes that usefulness is visual. Open the dashboard. See the chart. Edit the profile. Review the book page.
Sometimes it is conversational. Ask what changed. Create the link. Compare campaigns. Check what is missing. Get the relevant context without leaving the discussion.
Both modes should respect the same author.
The author should not have to become a technical operator to benefit from the conversational mode.
They should be able to ask normal questions.
"Which of my campaigns got the most store clicks last month?"
"Make a campaign link for my newsletter about the paperback sale."
"Which of my books still needs a Kobo link?"
"Help me improve my author profile based on the books I already have in Tutarium."
That is how authors already think about the work.
The interface should meet that language.
The point is less interruption
There is a version of software that asks to be the center of attention.
It wants you to log in, look around, notice all the features, admire the menus, and remember that the product exists.
Sometimes that is necessary. Often, it is vanity.
For many author workflows, the better product is the one that recedes at the right moment.
If you are making a careful edit to a public book page, the dashboard should be clear and dependable.
If you are planning a campaign in an assistant, Tutarium should be reachable from that conversation.
If you are trying to decide whether to repeat a promotion, the analytics should be available in the form that helps you decide.
If you simply need a clean link for the next newsletter, the product should not turn that into a small pilgrimage through tabs and menus.
This is not about making everything automatic. It is about reducing unnecessary interruption.
Authors already have enough interruption.
They balance writing with publishing logistics, retailer pages, newsletters, ads, cover decisions, pricing experiments, reviews, social platforms, series planning, and the strange emotional weather of trying to sell something personal in public.
The least software can do is avoid adding more ceremony than the task requires.
Fitting into the work
Tutarium's AI integrations came from noticing an existing behavior, not trying to invent a new one.
Authors are already asking AI assistants questions about publishing and marketing. They are already using conversations to think through launches, diagnose weak ads, plan newsletters, compare options, and make sense of the next step.
So Tutarium should be able to participate in those conversations when the author wants it to.
Not as the whole story.
Not as a replacement for the dashboard.
Not as a spectacle.
Just as another way to use the same book marketing system, in the place where the author's attention already is.
That is the product philosophy behind the work.
Technology is at its best when it fits naturally into the way people already work.
Authors are already using AI to ask questions about self-publishing and marketing.
Tutarium simply aims to be there when those conversations happen.