On its TrustMRR listing[1], Sleek is marked for sale. The asking price has changed from $666,666 to $500,000, alongside “2.5x revenue,” 7 interested buyers, and 3,027 views. The same page lists all-time revenue of $196,063, MRR of $17,672, and 519 active subscriptions. It says the revenue is verified through a Stripe API key.
A for-sale label says nothing about product quality. But alongside a number from the interview, it deserves another look: Pomelli says Sleek reached $10k MRR within a month of launch without spending a dollar on marketing.
First, what does it do for someone? Suppose you want to explain an app idea to a partner and need to show roughly what login, home, detail, and payment screens would look like. This is an illustration, not a particular customer's experience. According to the website[2], you can enter a sentence, paste a written requirements specification, or upload a reference screenshot you like. It picks typography and colors and plans the screens before drawing them, with a shared style across every screen.
The output is editable iOS/Android interfaces, including layouts, components, copy, and styling. If a screen does not look right, you can change it manually or ask for changes in chat.
This is closer to “AI draws your first version” than “AI designs your app.” It shortens the journey from an idea to a first set of editable screens.
Four design tools in a year; this one is mobile
In the Indie Hackers interview[3], Mattia Pomelli says he has been coding for about eight years and has always liked design. He eventually found that building design tools sits at the intersection of the two. Over the preceding year, he and two friends built four design tools. Sleek, their latest launch and current focus, took three weeks.
His reason for choosing mobile was straightforward: more people are starting to build mobile apps, while mobile has fewer coding and design tools than the web. He wanted to apply his accumulated design-tool experience to a narrower opening.
His focus is now on mobile-app interfaces, and that narrowness shows up in the product. The website's FAQ says it uses iOS Human Interface Guidelines, Material Design, native navigation, real device dimensions, and tap targets, producing something that feels more like an app than a website cropped to phone width.
It is not trying to replace Figma
The more interesting question is where the output goes. The website's FAQ says every plan can export React+Tailwind or plain HTML, or paste designs into Figma as native editable layers without a plugin. The free-plan table, however, marks code and Figma export as “Limited.” In other words, it wants the step before Figma: the design can go into your Figma file, your code, or your coding agent.
Image: From the product website[2], obtained on 2026-11-18.
The Pro and Team REST API and official agent skill are the part I find most interesting. The website[2] says coding agents such as Claude Code, Cursor, and Codex can autonomously create projects, generate mobile screens, and pull back Figma layers or React code. It is sold not just for people to click buttons, but for agents to call. Once design becomes a call to the interface, the paying customer may be the person writing code; a screen is just one step in that person's pipeline.
Charging in credits
The pricing page[4] meters usage in credits. Generating a screen costs about 30 credits; editing one costs 5–30, depending on prompt length, attached images, and whether images need to be generated within the design. Free is $0, with 60 one-time credits, 1 project, and 3 screens. Starter costs $29/month or $240/year, with 3,000 monthly credits, 5 projects, and unlimited Figma and code exports. Pro's early-bird price is $49/month, down from $99, with 20,000 credits. Team is $99 per person per month. Pro and Team users can buy 5,000 additional credits for $15 when they run out; those credits do not expire.
A free account can also try the agent once. The website's FAQ says the one-time trial credits are enough for roughly one design, and API generation uses the same credits as generation inside the app.
The payment terms[4] say subscriptions, credit purchases, and unused credits are nonrefundable except where required by law. Canceling a paid subscription leaves service available until the end of the period; canceling a free trial ends it immediately. These are not romantic terms, but they explain a business that collects payment upfront for an allowance.
Revenue makes a loud claim; profit remains out of sight
In the interview body, Pomelli says he reached $10k MRR within a month of launch without spending a dollar on marketing. The same interview's headline says “six weeks,” while its introduction says “two months.” The three timeframes disagree. There is no fourth source here to settle them, so they must stand side by side.
TrustMRR provides more detailed numbers, updated on 2026-11-17 at 03:47 PM without a specified timezone: all-time revenue of $196,063, MRR of $17,672, and 519 active subscriptions. The page title separately says “$16,737 in the past 30 days,” a different measure from either figure in the body, without explanation. These revenue and subscription numbers sit on a sale listing for potential buyers; “2.5x revenue” is also a buyer-facing valuation measure.
One point needs to be clear: MRR is not profit, 519 subscriptions do not mean 519 customers, and the page does not show the plan mix. AI-call, infrastructure, and payment costs, gross profit, and net profit are undisclosed. Whether the business is profitable remains unclear; what can be established is the revenue scale recorded on that page.
The website says it targets founders, product managers, marketers, and developers who need mobile-app designs without spending hours in Figma, and claims 60,000+ app makers have used it. Pomelli separately describes users as app founders or developers without design skills, or without the time and budget to hire a designer. These are self-reported descriptions; the paying share is not visible.
The same task, a different delivery destination
TapUI offers a comparison in the same category. Its terms of service[5] describe a SaaS that generates and refines mobile screens from text prompts and optional reference images, supports project history, and delivers Figma, HTML, and image-based handoffs. It explicitly does not export React Native, Swift, or Flutter code. Both products handle the same task: a sentence, an optional reference image, and mobile screens. The difference is where the result goes: Sleek offers native Figma layers and React+Tailwind/HTML; TapUI offers Figma, HTML, and PNG.
TapUI's current prices[6] are $200 annually for Starter, shown as approximately $17/month with 100 screens/month, and $320 annually for Pro, shown as approximately $27/month with 650 screens/month. Its own comparison blog post[7], dated 2026-10-06, lists monthly billing at $20/$40 and annual billing equivalents of $17/$27: another presentation of the same billing cycles. Someone sending designs to Figma wants something different from someone having an agent call the interface directly. The better fit depends on which step the pipeline connects to.
Sleek is not betting that AI can draw screens—that is no longer particularly hard. It is betting that design can become a call inside a pipeline. It is a clever position between an idea and Figma, code, or a coding agent, able to deliver to either end, but also vulnerable to either end reaching into its territory. A product built in three weeks next has to prove more than speed: how many people will still pay monthly for credits once they have an agent? The asking price on the sale listing is only supporting evidence.