For freelance developers
$ git diff --no-index webapp-proposal-old.md webapp-proposal-aeto.md
Win the project before you write a line of code.
Paste the client’s brief — or a GitHub repo link. Aeto drafts a developer-grade proposal — phased scope, tech stack, estimates, payment schedule, revision limits, IP terms. You check every number, then send it as a trackable page or PDF. Minutes, not evenings.
✓ ACCEPTED — client viewed 3×, signed in 2 days
The client can't read your code. They can read your proposal.
Every project starts the same way: someone asks “can you send me a proposal?” and three unbillable hours disappear into a Google Doc. It comes out vague, so you either lose to an agency with a polished document — or win, and discover the vagueness later, when “one small change” turns into week nine of an eight-week project. The proposal is where projects are won and where scope creep is born. It deserves better than being the thing you rush at 11pm.
How it works
A client email, a job post, a rough description — or a GitHub repo link, if the job is extending an existing codebase. Aeto asks one or two clarifying questions if the brief is thin.
Every estimate, phase, and clause is editable. Aeto learns your rates, your stack, and your standard terms — the second proposal sounds like you wrote it.
A clean web page or branded PDF under your name. See when the client opens it. Click-to-accept closes the deal.
The spec, standard.
Every Aeto proposal ships with six sections most freelance proposals leave out. Here’s what each one does for you.
1.0 Executive summary
The project in the client's language, not yours. The paragraph that makes a non-technical buyer feel understood before they read a single number.
2.0 Phased scope
Milestones a client can actually follow. Breaking the work into phases turns one intimidating quote into a sequence of yeses — and gives you clean points to get paid.
3.0 Recommended stack
The tools, with the "why" in plain English. "Next.js so it loads fast on mobile" reads as expertise; a bare tech list reads as jargon. It's how you justify the price without sounding defensive.
4.0 Estimates per phase
Time and cost split across the work, never one scary lump sum. Itemised numbers are harder to haggle down and easier to say yes to.
5.0 Payment schedule
Tied to milestones, so you're never carrying weeks of unpaid work. A deposit and staged payments are the difference between getting paid and chasing an invoice.
6.0 Terms
Revision limits, change-request handling, IP transfer on final payment. The paragraphs that stop "one small change" from eating week nine — the single biggest source of unpaid scope creep.
"Couldn't I just use ChatGPT?"
You could — and you’d get a generic document that reads like everyone else’s, with estimates it made up and terms it forgot. Aeto is opinionated about one thing only: developer proposals. It structures scope the way software actually gets built, keeps your rates and terms on file, formats a client-ready document, and tells you when it’s been opened. The highlighter, not the pen, is what you’re paying for.
What an evening of your time is worth.
The maths isn’t close. Aeto costs less than twenty minutes of your time and gives back most of an evening, every month.
Two ways in.
Free
$0
+ 2 proposals per month
+ Full dev-grade scope, stack & estimates
+ Edit everything, export to Markdown
· Sent with a small "Made with Aeto" footer
· No card required
Founding member
$29/mo
locked for life
+ Unlimited proposals
+ Your branding — no Aeto footer
+ Trackable send page — see when the client opens it
+ Branded PDF export & click-to-accept
+ Saved rates, stack & terms — every draft sounds like you
+ Direct line to the founder; vote on the roadmap
+ Price never increases
Planned public pricing: $49/mo · Agency tier $99/mo
Lock in $29/moThe free tier is genuinely free. The paid tier is for when you send proposals to real clients and want them to look like it.
FAQ
Do I still control the numbers?
Completely. Aeto drafts; you approve every estimate, rate, and clause before anything is sent. Nothing goes out without your sign-off.
Is this legal advice?
No. The terms sections are well-structured starting points used by working freelancers, not legal advice. For high-stakes contracts, have a lawyer review.
What about GitHub or Upwork?
You can paste a GitHub repo link at launch — Aeto reads the README, file tree, and dependencies to scope work on an existing codebase. Deeper repo analysis and importing from job posts are on the founding-member roadmap.
Is the free tier actually free?
Yes. Two full proposals a month, real dev-grade scope and estimates, no card required. Free proposals carry a small "Made with Aeto" footer and export to Markdown. You upgrade when you want your own branding and a trackable send page.
What does it cost after beta?
Founding members keep $29/mo forever. Public pricing is planned at $49/mo, with a $99/mo tier for small agencies. The free tier stays free.
Do you have a team plan?
An agency tier with shared templates, multiple seats, and team-wide rate settings is coming after beta. Founding members get first access and input on it.
When can I use it?
Founding members get beta access first, within the next few weeks.