FreighAI
FreighAI · Playground article
Playground · Checklist article

How do you size up a young software vendor, fairly?

Question D3 of the twelve. You are about to put a core process on somebody else’s software. If they are gone in eighteen months you run this whole exercise again, and the second time your team is harder to convince.

This article goes deeper than the sheet: what you are actually betting on, what a straight answer sounds like from a young vendor and from an old one, what you can check without asking, and where the decision really sits.

The short answer

Ask how long the vendor has done this, how many freight forwarders are live on the product, and who funds them. Straight numbers, however small, with honesty about their stage, is the answer you want. Size is not the test. Decide on whether you can leave with your history.

What are you actually betting on?

Three things, and they fail in different ways.

People say they are betting on the vendor, which is true and too vague to act on. Underneath that sentence are three separate bets. A company can be a good bet on one and a poor bet on another, and they are not equally within your control.

The three bets underneath the purchase
Bet oneThe company is still here

Funding, revenue and how many people it takes to keep the product running. The bet everybody discusses, and the one you influence least.

Bet twoThe product keeps up with your work

Whether it follows your lanes, your formats and your house rules as they change. A well-funded company can still stop developing the part you bought.

Bet threeYou can leave with the history

Your rates, quotes and customer list, exported in a normal format, on your own initiative. The bet you control, written in the contract rather than the pitch.

What you are betting on
What you are really buying when you sign with any software vendor: that the company survives, that the product keeps up with your work, and that you can walk away with your own history. The third one is written in the contract rather than the pitch.

Most buyers spend the meeting on the top layer and none of it on the bottom one, which is the only layer they own. Get the exit right and the size of the company matters much less. That is the most useful sentence on this page, and the rest of it is how to get there.

It is also why C1 and C2 sit on the same sheet as D3. If you can take everything with you, a vendor failing costs you an expensive quarter. If you cannot, it costs you a year.

What does a straight answer to D3 sound like?

Three numbers and a stage. That is all the question is asking for.

Question D3 in the room: what to ask, and what a fair answer sounds like.
  1. How long have you been doing this?
    What a fair answer sounds like
    The date the product started doing this job, not the date the company was registered. Plenty of software firms did something else first. Both dates are fine. Merging them is not.
  2. How many freight forwarders are live on it?
    What a fair answer sounds like
    A count of forwarders running real work today. Not accounts, not pilots, and not every kind of logistics company rolled into one figure.
  3. How many were live twelve months ago?
    What a fair answer sounds like
    The follow-up that turns a number into a direction. Four to eleven is a different story from forty to eleven, and the second story is the one a single number hides.
  4. Who funds you?
    What a fair answer sounds like
    Investors, revenue, a parent company, or the founders’ own money. Each brings a different set of pressures. None of them disqualifies anybody, and all of them are knowable.
  5. What stage are you at, honestly?
    What a fair answer sounds like
    A sentence a founder can say without flinching. “We are early, and here is what that means for you” is stronger than a growth story with no numbers under it.

Notice what is not on that list. Total funding raised is not a safety measure. A large raise buys time, and time is not the thing you need. What you need is a company that still cares about freight forwarding in three years. Ask what the money is for instead, and listen for whether this market is the plan or a stop on the way to a larger one.

Ask the count twice, in two shapes. “How many forwarders are live” and “how many sent a quote out of it last week” should land on roughly the same number. When they do not, the gap between them is the real answer.

What are the traps, on both sides?

There are four. Two punish a young vendor unfairly and two flatter an established one, and all four feel like prudence while you are doing them.

One. The count that is not forwarders

“Hundreds of customers” is not an answer to D3. Warehouses, hauliers, shippers and brokers are all logistics companies, and none of them is you. Ask for the number of freight forwarders, then for the number of freight forwarders your size, and expect the second number to be much smaller than the first at any vendor.

Two. The funding round read as safety

A raise is a bet somebody else made, on a different question, over a different horizon. It says salaries are covered for a while. It does not say the product will still be maintained, and a company with more money sometimes moves away from a small market faster rather than slower.

Three. Punishing the vendor who answers

Ask three vendors how many forwarders are live. One says eleven. Two say “lots”. If you shortlist the two, you have run an experiment on candour and thrown the result away. Score the answer, not the number, or you will teach every vendor you meet to stop giving you numbers.

Four. Assuming an established vendor cannot go

Older software leaves too. It gets acquired, folded into something larger, or the module you bought quietly stops getting attention while the price moves at renewal. Ask an established vendor what they retired last, and what the forwarders on it were offered when they did.

How do you check any of it yourself?

Some of the answer is public, free, and takes about ten minutes at your desk.

Whatever the vendor tells you, the company behind them has a registered existence somewhere, and that record is usually open.

  • The register where they are incorporated. The UK’s Companies House service publishes company information such as the registered address and date of incorporation, current and resigned officers, document images, mortgage charge data, previous company names and insolvency information, free of charge. Most countries run an equivalent.
  • The legal name behind the brand. Ask for it, or find it in the terms of service or privacy policy on their own site. A brand and a registered company are often different names, and your contract will be with the second one.
  • Recognition schemes, where a country runs one. In India, the Department for Promotion of Industry and Internal Trade issues a Certificate of Recognition that can be verified on its site to startups that qualify, and the number can be checked on the Startup India portal.
  • The people. Look at who builds the product and how long they have worked on this particular problem. A three-year-old company whose team has spent fifteen years in freight is not the same bet as a three-year-old company with none.
  • The product’s own trail. Release notes, a changelog, documentation with dates on it. Regular dated changes are evidence for bet two, and their absence is evidence too.

It is only fair to run that on the vendor whose website you are reading. FreighAI is the product of AggAiLabs Software Solutions Private Limited, based in Pune, India, holding DPIIT recognition DIPP232097. Those three facts are checkable in public records without asking us, which is the standard this section asks you to hold everybody to.

None of this stands in for the question. It changes what you do with the answer. Where the public record and the meeting agree, move on. Where they differ, ask about the difference, and pay more attention to how it is explained than to the difference itself.

What do you write down, and what goes in the contract?

One line per vendor the same day, and one clause before you sign.

Running D3 through a real call
    1. 01Ask the threeHow long, how many forwarders, who funds you.
    2. 02Numbers, or a storyWhich one you get is the finding.
    3. 03Ask about last year“How many were live twelve months ago?”
    1. 04Check the registerTen minutes, on your own, after the call.
    2. 05Fix the exitFormat, notice, and what happens on acquisition.
    3. GATEYou decideOn the exit and the direction, not the size.
FreighAIYour side of the callYour team approves
Ask the three, ask the follow-up, check the register on your own afterwards, then fix the exit before anybody talks about price. The decision at the end is yours, and it is a decision about the exit rather than the size.
Question D3, written down: one line per vendor, four columns.
  1. Live forwarders
    What goes in it
    The number they gave, beside the number for twelve months ago.
  2. Stage and funding
    What goes in it
    Where the money comes from, in one phrase, in their own words.
  3. Checked
    What goes in it
    What the public register said, and whether it matched the room.
  4. Exit
    What goes in it
    Export format, notice period, and what happens to your history if they are acquired.
Recommendation

Decide on the exit, not the size. A young vendor with a working export, a short notice period and a written clause about acquisition is a smaller risk than an established one with none of the three. Ask for the export during the trial rather than at signature, and have somebody open the file.

There is one number worth writing before the meeting rather than after it. What does this cost you if the vendor disappears in a year? If the honest answer is a few weeks of work and your data back, you can afford to buy from a young company. If it is a year of your operations team, you cannot, and no amount of funding on their side changes that arithmetic.

What is fair to a young vendor, and what is fair to an old one?

The same question for both, and a different benchmark for each.

Fair to a young vendor is accepting small numbers. Eleven live forwarders, stated plainly, with the name of one you can telephone, is a real answer to D3. Accept that some processes are not written down yet. What you are testing at this stage is whether the founders say true things when the true thing is unflattering, because that habit is the only protection you have when something goes wrong later.

Fair to an established vendor is refusing to treat age as an answer. Ask which forwarders your size joined in the last year, ask who maintains the part of the product you are buying, and ask what they retired last. Longevity tells you they survived. It does not tell you they are still investing in the thing you are about to depend on.

Where a young vendor should lose is the exit. If they cannot describe how you get your history out, their smallness becomes a risk you are carrying for them. Where an established vendor should lose is relevance. If nobody your size has joined recently, you are buying somebody else’s product with your own money.

Read D3 beside D1 and D2. D1 puts a forwarder your size on the telephone. D2 tells you what the product cannot do. D3 tells you whether the company will be there long enough for either to matter. Part D is one question asked from three sides, and no single side of it decides anything.

Questions

Common questions

01

Is it rude to ask a founder how they are funded?

No. It is a normal question in any supplier review, asked of insurers, banks and carriers without anybody blinking, and the answer is often already public. What you are reading is not the funding. It is whether they answer plainly or turn a simple question into a story.

02

How small is too small?

There is no general line, and anybody who gives you one is guessing. Set it from your own exposure. Work out what it costs you if this vendor stops trading in a year. If that cost is survivable and the export works, the number of live forwarders matters less than the exit clause does.

03

What if a vendor will not give me a number of live forwarders?

Ask why, and listen. “We are early and it is eleven” is fine. A confidentiality answer is worth testing: ask instead how many sent a quote out of the product last week, or ask them to have a customer tell you. If neither is possible, treat D3 as unanswered and weight D1 more heavily.

04

Does buying from a large vendor remove this risk?

It changes the shape of it. A large company is less likely to disappear and more likely to retire a product, move it inside a bigger suite, or reprice it at renewal. The questions about your export, your history and your notice period are the same either way.

READY WHEN YOU ARE

Take question D3 into your next vendor call

Ask for the three, ask what they were a year ago, then spend ten minutes on the public register when you get back to your desk. Decide on the exit rather than the size. Ask us D3 as well, and check our answer the same way.