Pembangunan

Anggaran Kasar Aplikasi / Sistem

Use skrin, peranan, pemberitahuan, aliran kerja, and integrasi to build a quick kasar anggaran.

See terbaik / mungkin / terburuk ranges, MVP cuts, and a shareable URL without leaving the pelayar.

  • Skrin, peranan, and integrasi are all weighted
  • Terbaik / mungkin / terburuk are calculated automatically
  • MVP cuts are ranked by impact
  • Hanya pelayar, tiada pelayan muat naik
Buka alat The initial load does not rewrite the URL. Use the kongsi button to create a link.

What this tool shows

  • Build a base usaha anggaran from skrin, peranan, aliran kerja, and external integrasi.
  • Tambah-on flags for luar talian support, pemberitahuan, audit logging, and pelbagai bahasa work adjust the difficulty.
  • Review usaha, duration, kos, and MVP cut candidates together.

Cara menggunakan

  1. Buka the tool and choose the project jenis and target platform.
  2. Enter skrin count, peranan count, aliran kerja count, and integrasi count.
  3. Toggle luar talian support, pemberitahuan, audit logging, and pelbagai bahasa work as needed.
  4. Adjust design level, QA level, the daily rate, and the perpuluhan paparan setting.
  5. Review the anggaran, then use the MVP preset, salin hasil, or kongsi URL actions.

Sampel

Standard business app

Input

8 skrin, 2 peranan, 1 aliran kerja, 1 integrasi, Web, standard design, standard QA, JPY 100,000 / hari

Output

About 11.5 hari-orang, 3 hari, ¥1,150,000. Terbaik 9.2 / terburuk 15.0.

Feature-rich multi-platform system

Input

18 skrin, 5 peranan, 4 aliran kerja, 3 integrasi, luar talian, pemberitahuan, audit logs, pelbagai bahasa, Web + Mobile, premium design / strict QA

Output

About 71.1 hari-orang, 16 hari, ¥7,111,000. Terbaik 56.9 / terburuk 92.4.

Anggaran inputs

Anggaran Kasar Aplikasi / Sistem

Your inputs stay in this pelayar and are never sent to the pelayan.

Tetapan

  • Project jenis - Switch the starting difficulty and delivery style.
  • Target platform - Web, mobile, and multi-platform projects carry different usaha.
  • Design level - Reflects how polished and custom the UI work will be.
  • QA level - Reflects test litupan, verification cycles, and fix loops.

Breakdown

  • Skrin count - Total senarai, detail, form, and tetapan skrin.
  • Peranan count - How many peranan you need, such as admin, user, or approver.
  • Aliran kerja count - Increase this when approvals branch or have multiple steps.
  • Integrasi count - API, webhook, and external SaaS connections.

Anggaran

Terbaik - person-days
Mungkin - Anggaran
Terburuk - Terbaik is 80% of mungkin; terburuk is 130% of mungkin.
Team capacity - 4.5 hari-orang / hari

MVP cuts

The most expensive items appear first.

Tiada obvious cuts from the semasa input.

  • Luar talian support - Luar talian support needs keadaan segerak and reconnect design.
  • Pelbagai bahasa - Pelbagai bahasa work adds salin and pengesahan usaha.
  • Audit log - Strict QA often adds planning and fix loops.

Catatan

  • This is a kasar-anggaran helper, not a substitute for a formal quote or contract scope.
  • Integrasi often tambah coordination work, API auth, webhook handling, exception paths, and retries.
  • Luar talian and pelbagai bahasa work expand the implementation and verification scope beyond skrin count alone.
  • Real projects should also account for legacy assets, reuse rate, and stakeholder review cycles.

Soalan Lazim

Can I use this as a formal quote?

Tiada. It is a planning-stage kasar anggaran. Ganti it with a formal quote once the assumptions are tetap.

Can kos go up even when the skrin count stays low?

Yes. Pelbagai bahasa work, integrasi, strict QA, and multiple platforms all increase usaha.

What does the MVP preset do?

It applies a smaller starter configuration that is closer to an initial release.

What is stored in the kongsi URL?

Inputs, selected options, perpuluhan paparan, and query segerak tetapan are stored.

Does the calculation send anything to the pelayan?

Tiada. Everything runs locally in the pelayar.

Pautan berkaitan