Aakalanआकलन

From an idea or a document to a cost range, step by step.

Six steps, most of them a single click. Aakalan's AI only reads and suggests; every number is worked out by a fixed set of formulas, so the same answers always give the same price.
  1. Choose how to start

    Upload the requirement document if you have one. If not, pick the kind of software: a public portal, software for your staff, an online store, a booking app, an AI chatbot or something else.

    A saved template starts you with an earlier estimate's answers.

    requirement-document.pdf · page 4

    4.2 Patients shall book, move and cancel appointments online, and receive an SMS reminder.

    Bookings · clause 4.2SMS reminders · clause 4.2
  2. Tick what it should do

    The usual features for your kind of software come first, with the most common already ticked. Write a few lines about it and Aakalan ticks the ones you describe, showing the words it matched. Anything missing, add it yourself.

    With a document, every feature found shows its page and sentence.

    Example estimateClinic booking app19% less with AI tools
    Likely ₹19 L
    ₹14 L₹26 L
    FeatureWithout AIWith AI
    Bookings and appointmentsStandard₹3.3 L₹2.6 L
    Online fee paymentBasic₹1.4 L₹1.1 L
    Mobile appBasic₹3.9 L₹3 L
    SMS reminders₹1.1 L₹0.9 L
    About 4 people for 3 months
  3. Answer about ten questions

    A first version or the full product, website or app too, how many people will use it, other software to connect, old data, where it runs and how long it should be looked after. One question per screen, in plain words.

    Not sure? Choose “Not sure”: we use the usual answer and widen the range.

    Question 3 of 10

    How many people will use it?

    Up to 100100 – 1,0001,000 – 10,000Not sure
  4. Add details if you know them

    How bad an hour of downtime is, a security audit, monthly reports, a ready design, how much the chatbot will be used, help at launch. Skip anything you don't know.

    Check every answer on one screen before calculating.

  5. Read the result

    The low, likely and high cost; the building cost of each feature with and without AI tools; the team by role and months to build; everything inside the price; costs paid to others; and similar real projects.

    Download the PDF report or the Excel bill of quantities to share.

    Team needed · example
    • Developer
    • Senior developer (checks AI code)
    • Tester
    • Designer
  6. Check what is not priced

    When you upload a document, Aakalan lists what it asks for that the estimate leaves out, such as penalties or warranty, and drafts questions to send the client about vague or missing points.

    Ask, update the answers, and calculate again for a narrower range.

    In the document, but not in this price
    • Penalties for delaypage 12
    • One year of warrantypage 13
    • Source code handoverpage 15

What happens to your document

It stays inside your organisation's account. The text is sent only to the AI service your company has set up, to read it, and is treated as data, never as instructions. Without an AI key, a keyword reader runs on our own server instead.

Where the prices come from

Day rates, cloud prices and service fees are stored with their source and date. Each estimate keeps the versions it used, so it never changes later; re-pricing at today's rates makes a new version. See all features.

Describe your software in a few lines and see what it costs.

Tick what it should do or upload the requirement document, answer ten short questions, and get the low, likely and high cost.