What to Send for a Software Quote
A software quote is only as honest as the packet behind it. If you send a slogan, you will get a number that hides a fight. If you send a job, an object, and the constraints, you will get a scope you can argue with. This is the packet Croncode asks for. Other studios should ask for something close to it.
Send a software quote packet with the user job, the object, who owns accounts, languages, and a not-now list. A slogan and a Pinterest board are not a brief.
What is the minimum packet?
- Job: who is stuck, and what “done” looks like in one session.
- Object: order, garment, case, journey, or your noun.
- Users: how many roles, not a TAM slide.
- Platforms: iOS, web, both, and which is first.
- Languages: English, Turkish, others, and who writes them.
- Accounts: who owns Apple, domains, and the repo today.
- Constraints: legal, payments, offline, on-device.
- Not now: at least five items you can live without.
If the work includes a model, add the AI brief from how to brief an AI app studio. Do not paste keys. Do not send live customer files to a personal chat.
What optional files actually help?
| File | Useful when | Skip when |
|---|---|---|
| Figma | Flows exist | It is only a mood |
| Store listing draft | You know the promise | It contradicts the job |
| Analytics | A product already lives | Vanity charts only |
| Brand PDF | Tokens exist | It is 80 pages of values |
A landing-page draft helps if the first release needs traffic. See landing pages that send traffic to the App Store. An ecommerce map helps if revenue is the point. See the 2026 checklist.
How do we read the packet?
We look for a first increment we could put on TestFlight. We look for a store gate if iOS is in scope. We look for a conflict between the promise and the not-now list. Process choice is separate: fixed scope vs agile. Sequence: idea to App Store.
If you are choosing a vendor, the packet also tests them. A studio that quotes without asking about accounts is a risk. See how to choose an iOS studio and studio vs freelancer vs agency.
When is the packet not enough?
When two founders disagree on the job. When the object has no owner. When the only success metric is a download count. We will ask you to pick. Data later should beat opinions. Related: users vs data.
What should you leave out?
- Fake urgency: “we launch next Friday” with no increment.
- Competitor clones: name the job they fail, not only their icon.
- Unowned inspiration: we will not copy another product’s UI as a deliverable.
- Secrets: production tokens, customer exports, ID scans.
Send it to the studio via croncodestudio.com/en. People who will read it: Goktug Unver, Yusufhan Sokur. What we build: what Croncode builds. Index: Journal.
If two founders disagree, send both versions labeled A and B. A quote cannot reconcile a hidden fight. We will ask you to pick one job. If you are hiring in Istanbul, add the diligence items from the Istanbul checklist so the first call is not a geography tour. If you already know you want a studio rather than a freelancer bench, say so. Models: studio vs freelancer vs agency. A one-page object diagram beats a twenty-page deck. Draw the noun and the systems that must tell the truth about it.
Frequently asked questions
Can I request a quote with only a voice note?
You can start that way. A number still needs the eight items written down. We will turn the note into a packet and ask you to confirm it.
Do I need a company registered before the quote?
You need to know who will own the accounts. Incorporation can follow, but the owner cannot be “we will see.”
Will you sign an NDA first?
We can discuss a mutual NDA. The packet above does not require your secret sauce. It requires the job.
How detailed should the not-now list be?
Five named features is enough. “Everything else later” is not a list.
What if I am still on no-code?
Say so, and say what you can export. See custom software vs no-code.
