Building Zestio in public • Sharing wins & losses • DM open
Joined June 2017
- Tweets1.5K
- Following747
- Followers180
- Likes1.6K
Pinned Tweet
day 15 of building in public:
continued working on my Agent Module. Testing different Routes and getting that thing working. Still a long way to get this working stable.
Hint: if you watch till the end you will see it fail 😅
every scheduling tool assumes the other side has an account.
> a viewing has 3 parties: owner, buyer, notary
> none of them will sign up just to say 'tuesday works'
so the invite is a link: pick a window, no account, and it expires.
which signup wall did you remove last?
the whole platform is one api. same credits, same endpoints, no separate api plan.
most tools sell you a ui and bolt an api on later. agents do not click buttons.
what is api-first in your product?
my product ships an MCP server, so an agent can drive it without me.
the hard part is not the tool list. it is that an agent needs the same guardrails a human gets: the credit cost of every call, and a hard stop when the budget is gone.
how do you price an api for agents?
ALT Zestio API quick start: a curl request to POST /api/enhance with a Bearer key
> floor plan and captions cost 0 credits - they finish a job you already started
> virtual staging costs 2, because it replaces an external service
> video costs 15, and it is the only function that costs me real compute per run
a 3D tour scan costs 8 credits. uploading a capture you already have costs 5.
same output, two prices - because the input work is not the same.
what do you price by effort instead of by perceived value?
400 german districts with land prices, rent levels and purchase prices on one page. every number carries a source and a date - no estimates, no smoothing.
the hard part was never the map. it was proving where each number came from.
what does 'a source' mean in your product?
most founders automate the product and hand-write the marketing.
the product has tests, a spec and a deadline. marketing has a mood.
guess which one gets boring first.
what did you automate this week that isn't the product?
spent the day building a market overview for german real estate:
> 400 districts with land prices + rent bands on one page
> no external map provider, so no third-party request leaves the browser
what matters more here is the boring part - one page, one number per district, no login wall.
what would you show a buyer first: the map or the numbers?
first slide of a carousel i built for german real estate agents tonight.
the hook has to hurt a little: "this flat is empty - and exactly that is the problem in the listing."
6 slides, one staging demo, zero photoshoots. how do you hook agents?
#buildinpublic
ALT Hook slide: Diese Wohnung ist leer. Und genau das ist das Problem im Inserat.
72 pages in my sitemap. 25 indexed.
> my homepage's only top-20 query is my own brand name
> the snippet google shows is english - my market is german
weeks of building, and i never checked how i look from the outside.
what does your outside view say?
#buildinpublic
day 85 of building in public:
got the email every solo dev loves: 100% of the free tier used. not users, not traffic - deployment storage.
also moved all 12 of my cron jobs onto one model - the new one quietly rejects structured JSON on the relay, so one side job had to stay on the old one.
my bundle never got fat from code. it got fat from files I forgot existed.
what's the dumbest thing you've found still shipping to production?
#buildinpublic