A US$20 hosting plan sent us a US$188.08 receipt.
That is not an accusation. It is actually a much more useful story about software infrastructure.
Vercel's Pro line on our September receipt was $20. Another team seat was $20. The expensive part was everything our software did around those subscriptions: $99.19 in Build CPU Minutes and $39.68 in Connect Triggers, plus storage and a long tail of smaller metered services.
The plan price told us almost nothing about our bill.
The architecture did.
This is the part of building AI software that product screenshots rarely show. Ariy&Co has AI teammates, a research system, social workflows, a growing operating database, generated media, deployments, cron jobs, and increasingly observable events. Every one of those nouns eventually becomes somebody's invoice line.
This account follows September receipts and records gathered on October 2, 2026. It is a look at one period of work, rather than a statement of today's plans or prices.
Vercel: the expensive part wasn't Pro
Vercel amounts in this section are in US dollars. The September 27 receipt covered usage from August 26 through September 25, with the next cycle's subscription lines included.
Total paid: $188.08.
Build CPU alone was $99.19. Connect Triggers added $39.68.
Deployment Storage was $5.96. Serverless Function Storage was $1.24. Vercel Agent, observability, memory, invocations, image optimization and traffic filled out the smaller lines.
Then came the two familiar numbers: $20 for Pro and $20 for an additional team seat.
That breakdown changed the question we were asking.
“Should we leave Vercel because it costs $188?” is not a very good engineering question.
“Why did this development and deployment pattern consume $99 of build CPU in a month?” is much better.
A few days later, Vercel's October 1 usage summary showed $20.15 in subtotal usage for the new cycle and only $0.15 current total after included credit. Build CPU was $4.30 at that point, compared with $12.32 at the comparable point in the prior cycle.
It was not a completed invoice, so we are not declaring victory. But it is already a better feedback loop: change how the system builds, then watch whether the billing shape changes.
Cost is observability too.

DataForSEO: research has a meter attached
On September 26 we added $74 CAD of DataForSEO API credit. With tax, the order total was $83.62 CAD.
On October 2, DataForSEO emailed again.
At the then-current average spending rate, it estimated roughly three days of API usage remained.
This one is easier to connect to what Ariy&Co was doing. Discovery, verification, retries and fallback lookups can all consume provider credit before a prospect reaches outreach.
That does not mean we can divide $74 by a prospect count and call the result “cost per lead.” The research system uses different providers, different effort levels, fallbacks, retries, and different amounts of evidence depending on what is being established.
But it does mean research volume is not free simply because Hermes is software.
Every decision about how deeply to investigate a business has an operational cost somewhere below it.
One of the jobs for the next version of the system is to make that relationship more explicit: what did we spend, on which research run, to support which downstream decision, and did that decision eventually produce an outcome worth the effort?
That is a much more interesting number than API requests per month.
Metricool: free cost us a limit
Metricool gave us a different lesson.
The account was on the free plan.
On September 25 it hit the plan's 20-publication monthly limit. The email was very clear: no more planner publishing until the next month unless we upgraded.
Cash cost: zero.
Operating consequence: not zero.
A free tier is excellent when the workflow is optional. It becomes architecture when the workflow depends on it.
The important part is what happened next.
Ariy&Co did not upgrade simply because the workflow had outgrown the free tier. On September 26, the product merged the decision to retire Metricool as an active publication and engagement dependency and move supported social paths toward direct Meta integrations.
That decision concerns publishing transport. Today we use Metricool only for metrics on Nia’s account. Remy’s account will not be connected, and we are not upgrading Metricool.
That does not make Metricool a bad product. It means the provider boundary mattered enough that the right answer for Ariy&Co was architectural rather than commercial.
The cheapest dependency is the one you can replace without rebuilding your workflow.

Creative generation became a budget category
A year ago “generated teammate imagery” would not have been a normal software line in a small company's operating stack.
For us it is.
Our creative workflow uses OpenArt and Higgsfield alongside other generation tools. Those tools are not experiments sitting beside the product anymore; they are part of how Ariy&Co creates and maintains a visual identity around Nia, Remy, Zyla, Aletheia and Hermes.
That creates a different cost question.
The unit is not only “one generated image.”
A bad generation costs credits too.
Identity drift costs another generation.
The wrong aspect ratio costs another pass.
A beautiful image that cannot survive a desktop crop costs more work.
A scene that looks convincing but violates the editorial truth model may be unusable entirely.
This is why our visual workflow is becoming asset-based rather than prompt-based. Approved references, canonical identity, crop requirements, provenance and reuse matter financially as well as aesthetically.
The prompt is probably the cheapest part.

Would we choose it again?
That is the question we want The Stack to answer in every issue.
Not “Is this tool good?”
Good for what?
For us, at this stage, with this architecture, at this usage level, with these failure modes?
A provider can be expensive and still be the right choice. It can be cheap and still create too much operational friction. It can be excellent at the thing it sells and still be the wrong system boundary for Ariy&Co.
And sometimes the answer changes.
That is why we are going to publish the tradeoffs beside the tools, not just the logos.

