Skip to content
MakerGain
← Back to cases

The client owns the code and pays the AI bill: SpaceAI360 builds automation you can take with you

Edited by MakerGainPublished: Article updated:

Founded by Shahdin Salman alone, SpaceAI360 builds portable AI workflows inside customers' own accounts. It handles parsing, OCR, field extraction, database checks, and ERP/CRM writes after a form, email, or file arrives, routing uncertain items to human review. Rather than generic AI consulting, he starts with the highest-friction bottlenecks, assigning deterministic steps to n8n and judgment steps to Claude.

A form, email, or uploaded file arrives. Attachments are parsed, images go through OCR, and a model extracts structured fields. Code then checks them against a database. Clean records go into the ERP or CRM; suspicious ones stay in a human-review queue.

This is one of three “common builds” on SpaceAI360's official AI-automation services page (AI Automation services[1]). That sequence is what it sells. Its Indie Hackers product page lists one founder, Shahdin Salman, and a business building AI agents and workflows (SpaceAI360 on Indie Hackers[2]).

The services page spells out the division of labor: deterministic actions such as triggers, API calls, and retries run in n8n; judgment steps such as classification, extraction, and drafting go to Claude, with outputs validated against a schema. Another build is “reports that write themselves”: instead of exporting CSVs on Monday morning, a scheduled workflow pulls data from Stripe, the CRM, and databases, reconciles it, and posts a written summary to Slack explaining which numbers moved and where someone needs to decide. The review queue is part of the product, not a patch. The website's FAQ says uncertain items go to review rather than automatic execution, with sensitive actions requiring a human checkpoint (website[3]).

Image: From the official product page[3], obtained on 2026-11-18, retaining the original interface. The website example does not represent a test in this review.

Another page applies the same structure to recruitment. A new application triggers the workflow; résumés, cover letters, and form answers become structured fields. An LLM returns scores, brief reasons, and flags against a role-specific rubric. Candidates over the threshold enter a ranked Airtable view; borderline cases go to human review instead of silent rejection. Qualified candidates receive a booking link by text message connected to the recruiter's calendar (case page[4]). The title itself says “Internal build,” and the Outcome section identifies an internal template adapted to a client's own ATS, scoring rubric, and recruitment stages. It discloses no customer deployment or quantified results. It illustrates the workflow's shape, not effectiveness.

He starts with the greatest friction

The predicament Shahdin describes in an Indie Hackers post is familiar: growing companies spend dozens of hours each week on repetitive operations, fragmented processes, and manual entry between systems. Off-the-shelf automation tools struggle as tasks scale or require complex logic, while hiring an engineering team to build custom pipelines is too expensive for lean teams (Building SpaceAI360[5]). His choice is to tackle the highest-friction bottlenecks first, such as lead handling and complex data synchronization, rather than sell generic “AI consulting.” He adds a judgment: reliable workflows depend on Docker, self-hosted infrastructure, and fail-safes, not just prompt engineering.

That helps explain the product's shape. Systems are deployed under the customer's own accounts and logins; the customer owns 100% of the IP and code, with no platform fee or lock-in (pricing[6]). AI and hosting bills go directly to the customer's accounts, typically $20–200 a month for a small team, with spending caps. An optional monthly retainer covers monitoring, maintenance, and improvements, not access; the system keeps working after cancellation. The homepage says “No retainers,” while the FAQ offers an optional retainer. What is clear is that it is not compulsory. But the pricing cards place setup and monthly fees side by side, without explaining tier by tier which monthly fee can be removed or which service it covers. That requires the specific contract.

The sales page also has a “don't hire us” list: wanting unsupervised AI from day one, changing the workflow every week with nobody responsible, or seeking only the cheapest build are poor fits. Unstable processes should be stabilized before automation. Its value is in stating the prerequisite: automation needs a process owner first. That is of a piece with reliability coming from backend architecture.

He mentions one acquisition tactic: showing customers working workflow prototypes that, in his account, compress hours of manual work into sub-second execution. The website's entry point is a Week 0 audit call, first mapping where the team's time goes, then providing a scoped, fixed-price plan whether or not the customer hires them. The ROI calculator shows results without requiring an email address (website[3]). Time first, price second.

Three cards are not the whole price list

The charges need separating. The three most prominent tiers on the homepage and pricing page—Starter at $1,497 setup plus $347/month, Growth at $4,997 setup plus $1,247/month, and Enterprise from $18,000 scoped plus from $3,000/month—describe chatbots: single-channel FAQs, multichannel service with CRM sync, and multidepartment human handoff. The FAQ says an optional retainer covers monitoring and improvement, paid separately from access, with the system remaining usable after cancellation. How those three cards' monthly charges map to that retainer is not specified tier by tier.

The form, email, and attachment intake workflow above corresponds instead to the AI-automation services page: a single-workflow build starts at $997 setup plus $297/month, including monitoring; a multi-workflow system is $2,497 setup plus $797/month (services page[1]). The same site has a range-comparison table covering six services, with broader Starter, Growth, and Enterprise ranges and a common overage policy: Starter is charged at cost plus 20% above its limit, Growth at cost plus 15%, and Enterprise by custom capacity planning. These numbers cannot substitute for one another.

The same workflow can also be built in-house. n8n officially charges subscriptions by monthly workflow executions and offers a self-hosted Community edition (n8n pricing[7]). After paying for software, workflow design, connecting judgment steps, failure retries, and handover documentation still fall to the customer's team. SpaceAI360 sells scoped building, integration, and handover inside customer accounts, plus optional monitoring. These are different kinds of charges. n8n's subscription cannot be used to convert this company's quote or establish which is cheaper.

On revenue, the founder reports SpaceAI360 reaching $1,000/month in MRR (post[5]). The product page's revenue chart on the same platform shows $1k in July 2026, no data for August, and $1k in September, labeled as self-reported monthly revenue excluding the current month (revenue page[2]). The post displays no publication date, so it cannot be aligned with those chart months. Costs, profit, and customer count are undisclosed; those figures establish only that someone is paying.

Maintenance without lock-in

SpaceAI360 has a clear business shape: a one-time build charge, a system left in the customer's accounts, and the ability to take it away. Another continuing charge listed on the website is the optional monitoring-and-maintenance retainer. Usage above capacity limits is separately charged at a markup on cost, so recurring revenue is not maintenance alone. The FAQ gives the reason for the business: APIs change, edge cases appear, and prompts need adapting to business changes. It suggests budgeting 10%–15% of build costs annually, also describing what the monthly retainer covers (services page[1]). That is both a budgeting reminder to customers and an account of renewals based on changing workflows rather than lock-in. The website discloses no renewal or retention figures; this is an inference about the business model, not a validated result.

Continue reading

AI productivity
Over 180,000 views, 1 February sale: AI Renamer leaves batch-renaming confirmation to people

Ozgur Ozer's AI Renamer gives content-based names to opaque filenames such as DSC_0412.JPG and scan_20250312.pdf. For manual batches, people inspect the suggested names before pressing Rename All; nothing changes on disk beforehand. Ozer had always given away his small apps and first used Polar to solve payment collection because Turkey had no Stripe support. His first post exceeded 180,000 views but produced 1 sale that month; sales began coming after local support and a Product Hunt launch.

AI productivity
After closing a product nobody wanted, they broke entrepreneurship into “the next step”

David Heikka and his brother Felix launched their first AI form product and found zero demand. They tried ads, landing-page changes, renaming, and added features, then closed it after six months. They went on to build Buildpad, breaking business creation into stages that indicate what to validate next. Its early and current billing mechanisms differ, and the product was renamed aicofounder before changing back to Buildpad.

AI productivity
It writes your emails, but stops at LinkedIn

According to its website’s workflow, DeepReachAI finds people, researches recent developments, writes messages, classifies replies, and books meetings for cold outreach, while excluding automatic LinkedIn sending, WhatsApp scraping, and calls without consent. In an IndieHackers post, founder Aryan Agrawal said he had expected personalization to be the hook, but the compliance boundary—no automatic LinkedIn sending and no WhatsApp scraping—was what made people connect accounts. The homepage says Orio can send a first email through a connected account, without identifying the account provider.

AI productivity
An assistant cost thousands of US dollars a month. He put AI to work and reached $10k+ MRR

Because an assistant would cost thousands of US dollars a month, Elie Steinbock built an AI email assistant instead. It connects to an inbox, sorts messages, and drafts replies using email history, calendars, and customer records; a person still presses Send. On Product Hunt launch day, he emailed 20,000 newsletter subscribers and posted a video on his YouTube channel with 2,000 subscribers. He estimated that these extra efforts may have added fewer than 50 votes—a judgment, not a measured result.