Hi Hassan,
We covered most of these on the call — I've marked your answers inline so we both have a record. A handful are still pending (mostly the samples and a couple of figures); the green callouts show what we locked, the amber ones show what's still open.
Updated after Meeting 2:
Your answer
Same price for everyone. No trade-vs-retail split. Simplest possible model — confirmed.
Your answer
20% across everything you actually stock. Industry has 0%/5% items but not in your range.
Your answer
None currently. Accountant gets bank statements / invoices / statements each month manually. You're planning to change accountants — we'll revisit the integration question then. For now, an Excel export per month is enough.
Your answer
Yes, negative stock allowed. Customer can buy 50 bags of cement even if the system thinks you only have 30 — common in the trade because goods are often in the yard before they're booked in.
Your answer
Not tracked formally — current system can't do it. You're thinking about opening a "damaged sale section" at reduced prices instead of writing the value off. We'll bake this into the new system as a small revenue line.
Your answers
Statements: not currently sent ("we should but we don't"). New system will send monthly.
Late fees / interest: none, and you want to keep that policy.
Over-limit at till: block the credit-extension (they can't add more to their account), but allow the sale if they pay cash/card. Clear spec — exactly what we'll build.
Your answer
Manager-only. Standard model — staff send refund requests to owner/manager. New system will enforce with a manager PIN.
Your answer
No discounts by any staff member. Manager/owner only — stricter than my default. New system will give staff zero discount authority and prompt for manager PIN if needed.
Your answer
Mixed tender: already supported by the current system, will support it in the new one.
Suspended sales: you don't use them — staff finish the current sale and start a new one for any added item. We'll match that.
Your answer
Summer — building season + DIY rush. Avoid for cutover.
Your answer
Christmas / winter generally. Best candidate window for any pilot or bigger cutover work.
Update from Meeting 2
Stock count is already in progress and will be multi-month — not a single date. We'll align cutover per product category as the count for that category stabilises, rather than waiting for one big "stock-take complete" moment.
Your answer
Three partners, all must agree. You put the proposal to all three, they have a private discussion, then any one of them comes back to you with yes or no. So the one-pager has to convince three people who read it independently.
Update from Meeting 2
You deferred to your gut on the call, but the shape you kept reaching for was: low first commitment, new till running parallel to the old, monthly installments. That maps to Option E (pilot first) followed by Option C (monthly POS-as-a-Service) from the business case page. We've reordered the public business case so those two lead.
Net of all of the above, the gating items for the proposal are now: the Magnum product export, the four hardware/reporting samples (36–38), and the credit-transactions-per-week volume number. None of them block me from drafting the owner one-pager and the Phase 1 mini-SOW — I'll start on those today.
Speak soon,
Ilya