Sazinga
From the quotation to the cutting list, without rebuilding the job
Your quotation already knows what the job consumes. Turning that into a bill of materials and a nested cutting list without rebuilding it by hand.
Sazinga
GST on a fabrication quotation — what goes in the taxable amount
Where transport and installation sit relative to GST on a fabrication quotation, CGST and SGST versus IGST, and the ordering that changes the total.
Sazinga
How to price a stainless steel work table
Cost a six-foot stainless work table step by step — sheet weight, tube, hardware, labour and margin — with every figure shown so you can check it against yours.
Sazinga
Margin on selling versus markup on cost — the ₹900 a table nobody notices
Margin on selling and markup on cost are not the same twenty per cent. The arithmetic, the conversion table, and what the confusion costs over a year.
Sazinga
SS 202, 304 and 316 — what actually changes in your quotation
SS 202 against 304 against 316 for fabricators — what differs in the metal, where each grade belongs, and the price spread on one identical table.
Sazinga
What quotation software for fabricators actually needs to do
Quoting software for manufacturers mostly assumes a catalogue. Made-to-order work needs something else, and here are six tests to run on any vendor demo.
Sazinga
Why your quoting spreadsheet eventually lies to you
Estimating spreadsheets fail in predictable ways — copied files, stale rates, hidden assumptions. Where quoting in Excel breaks, and what fixes it.
Sazinga
Hoarding, unipole, gantry: OOH formats and sizes in India
What a hoarding, unipole, gantry and pole kiosk actually are, the sizes each is commonly built at, and why there is no single standard size.
Sazinga
How to start an outdoor advertising business in India
The two kinds of outdoor advertising business, what each needs to start, the permissions involved, and the three numbers that decide if it works.
Sazinga
Card rate, net rate and commission: how OOH pricing really works
Card rate versus net rate, how agency commission is applied, what printing and mounting really cost, and how to quote so procurement cannot argue.
Sazinga
What billboard management software actually needs to do
Why most billboard software solves the wrong problem, the eight things an out-of-home system must do, and the questions to ask before you buy.
Sazinga
How many days did your sites sit empty last month?
Vacancy is the biggest cost in an out-of-home business and the one nobody counts. How to work out what your empty hoarding days actually cost.
Sazinga
One hoarding, two clients, the same month
Double-booking an advertising face is almost never carelessness — it is a hold nobody confirmed. How it happens, and how to make it impossible.
Sazinga
"Send the photo" — and the hunt that follows
The proof-of-display photograph usually exists; finding it is the problem. What a client is really asking for, and how to answer in thirty seconds.
Sazinga
The proposal that took ten minutes
Out-of-home work is lost on turnaround and completeness, not on rate. What belongs in a proposal, and how to stop it taking a whole evening.
Sazinga
What billboard advertising actually costs in India
What hoardings, unipoles and gantries fetch across Indian markets, the five things that set the rate, and how to price your own inventory.
Sazinga
Why out-of-home payments get stuck, and what actually unsticks them
Payments freeze because the invoice and the purchase order describe different things. Where that mismatch comes from, and how to remove it.
Sazinga
The 3D preview is generated from the same inputs that produced the price, and stored nowhere
Dimensions and features already sit on a quote line. Turning them into geometry needs an archetype layout and a registry keyed by code, not a modelling pipeline.
Sazinga
A column named id is a naming convention, not a type
Converting forty key columns to a single id format, three of them had to be reverted, because what they held was a handle, a display name and a mixed bag.
Sazinga
A hundred hardcoded defaults, and the cause was a permission a field rep does not have
The clients hardcoded language, timezone and currency everywhere. The only endpoint holding the real values needed a permission a sales rep never gets.
Sazinga
A draft invoice must not have a number, and a sequence cannot give you a gapless one
Auditors ask why invoice 41 is missing. A database sequence will make holes, and a number allocated at draft becomes a hole the moment the draft is discarded.
Sazinga
A filter your API ignores is worse than a filter that returns an error
Two endpoints silently discarded the customer filter and returned every customer's pricing. The framework was doing what it documents, on every route, forever.
Sazinga
A missing translation key is not an error anywhere, which is why users see them
Forty-seven error codes the API could emit had no copy in the portal, so users read raw key strings. Nothing in the stack treats that as a failure.
Sazinga
A permission called "read your own certificates" does not know whose certificates you are reading
The gate proves you may perform a kind of action. It says nothing about which rows, and in eight handlers the row restriction was eight copied lines.
Sazinga
The public quote link reuses the exporter, so it cannot leak anything the PDF would not
A no-login share link is a new way for internal costs to escape. Building it on the redaction the exporter already does removes a whole class of mistake.
Sazinga
A compliance register is not a list of obligations, it is a rule that produces a list
The first model was a person, a certificate and an expiry date. Then came a register of 184 obligations across 15 domains, almost none of them certificates.
Sazinga
The repository had a script to fill in the numbers the product was meant to compute
A backfill and a validator, both carefully written, both compensating for an aggregation job that was specified in a schema comment and never built.
Sazinga
A shared test tenant is global mutable state, and it fails like global mutable state
Two suites invited members and never removed them. Nineteen accumulated, the seat limit tripped, and unrelated suites started failing on a rule they never touched.
Sazinga
The status column said active, and nothing had looked at it since the day it was written
A credential row carried both an expiry date and a status label. Only the date changes meaning as time passes, so every query had to distrust the label.
Sazinga
A view runs as its owner, which is how row-level security gets bypassed by a report
Row-level security on the base tables does not protect a view over them. The default is owner privileges, and an aggregate leak looks like a slightly high number.
Sazinga
An in-app assistant that cannot call out, because the index is the customer's entire pricing model
Designing a retrieval assistant to run on the same host as the application, on two shared cores with no accelerator, and to fail closed rather than fall back.
Sazinga
An endpoint nobody can reach is not a feature, and a search box that does not search is worse
A field-force product where a rep could not take an order on the phone. The API was complete, the module was marked done, and the flow did not exist on any client.
Sazinga
The import produced 2,698 rows where I expected 2,800, and the difference was the whole point
A clean import run proves nothing. Reconciling every entity count against the source, and naming the cause of every difference, is what proves it.
Sazinga
An invoice that is not real until a third party says so
Statutory real-time invoicing turns each sale into a distributed transaction with a regulator. The first design put the network call inside the sale transaction.
Sazinga
Append-only is a database privilege, not a coding convention
A draft function set a row's identifier after inserting it. The table had UPDATE revoked, so the schema would have rejected code that every review had passed.
Sazinga
Bulk import is a second front door to every write endpoint you have
One permission to import, and the target resource named in the request body. That combination lets a role create records it has no permission to create.
Sazinga
Adding millimetres to an inch-based pricing engine without touching a single stored number
Every pricing rule assumed inches. The customer wanted to enter millimetres. Converting at the API boundary was the only change that could not corrupt old quotes.
Sazinga
Development mode and release mode are different programs
The first release build of the mobile app failed on two configuration bugs weeks old. Development mode had never touched either code path.
Sazinga
Every question was correct and the whole set was broken
A hundred and fifty multiple-choice questions all had the answer in the first position. Each one was right. The distribution was the defect.
Sazinga
A pricing language with two keywords, because the third one would have been a mistake
Thirteen of 362 pricing rules needed to call other rules and branch on a dimension. Keeping the language to CALL and CASE is what kept it safe.
Sazinga
Two rows in the prospect list were the same business, and every useful column was generated
A scraped and model-enriched dataset looks like research. Separating observed fields from generated ones stops you building for a customer who does not exist.
Sazinga
Half a delimiter is a perfectly normal thing to receive
A marker protocol let one reply carry both chat and a draft. Truncation delivered the opening marker without the closing one, and the raw marker reached the screen.
Sazinga
I reported a build as passing, and it was the exit code of the command I piped it into
The build output was long, so it went through a pager. The pipeline reported the pager's exit status. The build had failed and the report said it succeeded.
Sazinga
The document number was six digits of a clock, and the retry loop was the giveaway
A comment said the numbering scheme avoided race conditions. The loop underneath it retried on duplicate key ten times, which is what you write when it does not.
Sazinga
The local database was production, and a typo of mine is the only reason it survived
A tunnel makes a remote database answer on localhost. That is what it is for, and it is why every migration run that afternoon went to the live system.
Sazinga
Logging out cleared a variable in the browser, and the token stayed valid for eight more hours
There was a sessions table with a revocation column and a token hash. Nothing ever wrote a row to it, and nothing ever read one.
Sazinga
Fifty-seven screens do not divide into seven workers without a foundation
Every contract bug in the project so far had been between contributors rather than inside one, so the rebuild started by making the seams mechanical.
Sazinga
Not set and zero are different answers, and one input box cannot hold both
A reorder level of zero means alert me when it runs out. No reorder level means never alert me. The empty string coerces to zero and the distinction is gone.
Sazinga
The notifications were correct, and every one of them went to nobody
Nine send points, each carefully guarded, firing into an empty token table because the app had never called either registration endpoint.
Sazinga
The software was multi-tenant on day one and onboarding a second tenant was still a project
Tenant isolation is the easy half. If loading a customer's pricing rules needs a developer, your customer ceiling is your developer capacity.
Sazinga
The same end-to-end suite runs before the push and after the deploy, pointed at a different host
Pre-push tests and post-deploy checks are usually two suites that drift apart. Parameterising one suite by base URL removes the drift and the second suite.
Sazinga
Only a server that answered should spend a retry
A phone out of coverage for a day burned its retry budget on failed connections and parked a valid order as rejected. That is the loss a queue prevents.
Sazinga
Price the feature, not the product, or your catalogue grows faster than you can maintain it
One made-to-order product had 24 features and 62 variants. Pricing at product level is combinatorially hopeless; pricing per feature is not.
Sazinga
The pricing spreadsheet had twelve formulas that were referenced but never written
What auditing a fabricator's quoting workbook revealed about how bespoke pricing really works, and which parts of it a person was silently holding together.
Sazinga
Three of the customer's own quotations told me more than the requirements call did
The output document is a specification. Reading real ones confirmed eight pending requests, produced several more, and settled two arguments about tax.
Sazinga
Redacting the payload and not the diff means you redacted nothing
The audit trail masked the request body and stored the before-and-after values in clear. Then the viewer rendered two masked values as "nothing changed".
Sazinga
Remove and Add are not inverses, so the child came back as a stranger
Removing a child archived the row. Adding her back created a new one. Her whole history stayed behind, and her old tablet credential stayed live.
Sazinga
Run every pricing formula twice, once on cost and once on selling, and never mix the results
Knowing what to charge is not knowing whether the job is worth taking. Two evaluations through the same rules give per-feature margin without a second engine.
Sazinga
A site is not a type, it is a set of capabilities, and the difference shows up in month two
One building held a press, a store and a shop. A type column forces a choice; a capability set does not, and the check reading it used the wrong operator.
Sazinga
Six quizzes created 0.6 seconds apart, and the child was served the wrong one
A stale closure in a loop created six rows where one was intended, and an unordered query picked whichever of them the database felt like returning.
Sazinga
Soft delete needs a taxonomy of children, not a decision per table
Deleting a product left 211 orphaned price entries and 104 orphaned variants. Fixing the product path missed the variant path, which orphaned exactly the same rows.
Sazinga
Store the working, not just the answer, and features you have not thought of become cheap
Keeping the full evaluation trace on the quote line paid for itself twice — in explaining old quotes, and in a bill of materials nobody had planned for.
Sazinga
The backlog said it was not built, and it had shipped weeks earlier
A gap register sent two people to rebuild an offline layer that already existed. It was wrong six times, and each entry was wrong in the same specific way.
Sazinga
A check constraint made over-delivery impossible to record, and lorries do not read constraints
The received quantity could not exceed the ordered quantity. That is a policy, not a fact, and the warehouse hit it the first time a supplier sent a full pallet.
Sazinga
The capability check ran for employees and skipped the owner, who chose the site himself
A middleware validated that a site could take till transactions. It returned early for account owners, and owners were the only ones who could name the site.
Sazinga
The dashboard guessed whether the number was a percentage, and turned 1% into 100%
A helper decided a stored value was a fraction if it was between zero and one. The one organisation that most needed the alarm got a perfect score instead.
Sazinga
A credential expiring today was in neither the expiring list nor the expired list
Four places asked "is this about to run out" and four expressions answered. Two excluded today, one included it, and one forgot to exclude revoked records.
Sazinga
The deploy printed a warning, then printed Done, and the old code kept serving
A restart step that could not get the privilege it needed logged a warning and carried on. Every deploy reported success while changing nothing.
Sazinga
Fourteen fabrication drawings, every one stamped not to scale, and what they could still prove
The CAD files looked like the authoritative source for dimensions and geometry. They were neither. What they were useful for was checking the formulas.
Sazinga
The uniqueness rule was doing concurrency work and nobody had noticed
One dispatch per order was a scope decision. Removing it for partial shipments exposed a race where two dispatches could each ship the last unit.
Sazinga
The model worked with my key and with nobody else's
A pinned model returned 404 for every newly created key while still appearing in the provider's own model list. Availability is a per-account fact.
Sazinga
The model gets a verdict field and the person gets a signature field, and they never merge
Reviewing 362 business-authored pricing rules needed an ordering, not an oracle. Keeping the AI verdict in its own column is what made it safe to use.
Sazinga
The quiz score was a fine proxy for reading, except on the lessons that mattered
A proxy metric that works on average can fail completely on one part of its domain, and the part it fails on is often the part you added it for.
Sazinga
The readiness screen reported 1,081 missing pricing rules. About 33 of them were real
A completeness dashboard counted every variant of every feature as required. The import was fine; the counting rule was wrong, and it hid the real gaps.
Sazinga
The tables existed, the columns existed, and not one route served them
Seventy-five endpoints, all parent-facing. The child's half of the product had a schema, a plan and a design, and no server to talk to.
Sazinga
An enforcement rule with no operator surface is an outage waiting for a date
Twenty-five of thirty-five test suites went red with no code change. The shared tenant's trial had expired four days earlier and nothing had said so.
Sazinga
Three code paths decremented the same stock column, and only one of them took a lock
A sale, a production run and an adjustment all wrote the same inventory row. One took a row lock, one wrote a ledger entry, and one did neither.
Sazinga
TRUNCATE CASCADE does not delete related rows, it empties related tables
Resetting the tenant data wiped every system role and every permission grant, because one nullable column made the roles table a child of the organisations table.
Sazinga
Twelve of fifteen questions, and a sentence saying which three are missing
Ask a model for fifteen items and you may get twelve. The choice is between failing, quietly shortening the list, or returning the twelve and saying so.
Sazinga
The lesson needed two facts to be true, and the screen only asked for one
Publish was a button. Assign was an item in an overflow menu on another screen. The child's tablet needed both, and said nothing when it had one.
Sazinga
A material grade sometimes changes the rate and sometimes changes the whole calculation
The source workbook had two formula columns per row, one per grade. That single detail decides how a bespoke pricing engine has to resolve rules.
Sazinga
An action belongs in an offline queue only if a replay can be proved either way
Offline delivery capture was a fiction, because the screen that records it could not be opened without a connection. The queue worked. Nothing could reach it.
Sazinga
The constraint names remembered a table that no longer existed
A production output table had a nullable parent column, an old parent beside it, and two identical foreign keys — one migration, told three ways.
Sazinga
Your sync cursor cannot be a timestamp, because timestamps are not unique
Rows written in one transaction share an update time to the microsecond. A greater-than cursor drops them and a greater-or-equal cursor repeats them forever.
Sazinga
A zero tax rate fell through to a hardcoded default, because zero is falsy
Three fallbacks in one expression, ending in a statutory rate typed into a route handler. A zero-rated sale skipped the first two and got taxed at the third.
Sazinga
Five AI providers configured, half the requests failed, and only one was ever tried
A fallback chain that advances on error codes but not on empty responses is not a fallback chain. It is one provider with extra configuration.
Sazinga
The click that did nothing was writing to a row nobody reads
An unordered single-row lookup on a non-unique key is not a bug that throws. It is a bug where the user presses a button and the screen ignores them.
Sazinga
A pending row is a promise, not a payment
The same mistake bit a rental ledger three times in three months — a field naming an amount was read as proof the amount had moved.
Sazinga
A status only your own app can change will never be true for long
A dashboard tile read 86 open jobs for one driver. Three were open. The other 83 had ended in ways the app was never told about.
Sazinga
A green test nobody has seen fail is not evidence
Seventeen layout tests passed against a stylesheet that made the assertion impossible to fail. Fifty-one screen tests passed on a portal that was entirely read-only.
Sazinga
An audit log that tells you which events it does not understand yet
Hand-written audit calls get forgotten, and a forgotten one makes the whole log untrustworthy. Capture centrally, label by registry, and mine the unlabelled.
Sazinga
Availability is a question about a date, and the picker was answering about today
A salesperson pitching a campaign that starts next quarter does not care what is free this morning. Availability needs a date argument, not a boolean column.
Sazinga
Store everything in UTC, but never decide anything in it
A test proved expired discounts still applied. The test was wrong, the bug was real, and both came from treating a business date as an instant in time.
Sazinga
Signature scanning found nothing. File integrity found 211 malicious files
A malware scan that returns zero hits is not evidence of a clean site. Comparing files against the official distribution is what actually finds things.
Sazinga
67,000 photos already labelled by humans, no GPU, and no model training
Embedding existing labelled data into class prototypes gives you a classifier in an afternoon — and a confidence margin that knows when to ask a person.
Sazinga
Making a cross-tenant reference physically impossible with composite foreign keys
Tenant isolation enforced by WHERE clauses depends on nobody forgetting one. Enforced by the schema, a cross-tenant row cannot be written at all.
Sazinga
We deleted four hundred and eighty files before writing a line of the new system
An approval step no expense could reach. A module nobody opened. Rebuilding around the real workflow started by removing everything that was not it.
Sazinga
The cheapest way to secure a brochure site is to stop running an application on it
Two compromised sites were rebuilt as static HTML with no interpreter and no database. The attack surface did not shrink — it stopped existing.
Sazinga
A receivables ledger that was seeded once and then quietly stopped being true
Two tables held outstanding amounts. Nothing kept them in step with the invoices they came from. Pay an invoice and the ledger never noticed.
Sazinga
The app was organised like filing cabinets and the people using it were running a process
Nine modules named after data types. One job — book a hoarding and bill for it — spread across three of them. That is why software feels scattered.
Sazinga
A pricing engine where the business owns the formulas and the code owns nothing
362 pricing formulas, none of them in the source code. How to evaluate business-authored expressions without eval, and why that boundary matters.
Sazinga
They were building the client's deck by hand in a presentation tool every single time
A proposal is a slide deck and a cost sheet. Generating both from the same records that produce the booking removes an afternoon of retyping per pitch.
Sazinga
Never store a balance. Store the entries that produce it
A mutable points column looks simpler for about a week, and then a retried request pays twice and nobody can explain where the balance came from.
Sazinga
The first real card payment was credited twice, 434 milliseconds apart
A read followed by a check is not a guard. Two webhooks for one payment both passed it, and the customer's account was credited double the amount.
Sazinga
The receivables card said zero and the database held forty-five unpaid invoices
Fixed-precision money columns come back from the driver as strings. Add them with the wrong operator and the total is silently not a number.
Sazinga
The booking rule that blocked eight paying clients, and why it was a bug and not a missing feature
A digital screen loops six to eight adverts at once. The system allowed one. That is a correctness defect, and it should be sequenced like one.
Sazinga
The one convenience that turned a single breach into an estate-wide one
A shared password reused across every database on a server is not a weak password problem. It removes the boundaries you thought you had.
Sazinga
One shared process pool is how a single compromised site reaches all the others
Shared hosting is usually presented as a cost decision. It is a blast-radius decision, and the bill arrives all at once when one site falls.
Sazinga
One question, nine implementations, eight of them wrong
Who is this leg assigned to? Nine places answered it independently. Eighty-one legs got an arbitrary answer and eighteen invented a driver who was not there.
Sazinga
How to store a booking that has no end date without breaking every date query you own
Runs until the client stops" is a real commercial term. Storing it as a null end date breaks overlap checks, calendars and availability all at once.
Sazinga
Filter the LLM's tool list by the user's permissions, not its output
A model that cannot see a tool cannot call it. Building a natural-language interface where authorisation is structural rather than a prompt instruction.
Sazinga
Read-only sight of money is not authority over it
Replacing two hard-coded roles with 77 granular permissions, and the design bug that would have shown field staff the director's dashboard.
Sazinga
You finish the booking and the software just stops
The data was a chain and the interface was a set of dead ends. No record linked forward to the one it produced, so every step meant going back to a menu.
Sazinga
Your permission model probably stops at the ORM and the CSV export walks straight past it
Row-level security kept tenants apart. Nothing kept a branch-scoped user from exporting the entire organisation's customers, orders and payments.
Sazinga
The deposit doubled because the payment landed beside the expectation, not against it
A customer paid a five thousand rupee deposit and was immediately asked for it again, because the ledger recorded the receipt as a new row.
Sazinga
The offline queue marked lost orders as delivered, because every 409 looked the same
Offline-first only works if the client can tell "already applied" apart from "rejected". A single conflict status collapses both into one answer.
Sazinga
The backup job failed silently for four days and four separate things were wrong
Certificate renewal had been dead for months behind a cron entry that looked like cover. A backup wrote nothing. Neither failure produced a single alert.
Sazinga
The thing you sell is not the thing on the map
A hoarding is a location. What a client buys is a surface, for a window, at a rate. Conflating the two puts the overlap check on the wrong row.
Sazinga
A permission check that was always false, and why nobody noticed for months
A UUID compared against a list of strings is never equal. The check failed closed, denied everything, and looked exactly like correct behaviour.
Sazinga
A not-null foreign key is a business rule, and this one was not true
Every invoice had to reference a booking. The business raised invoices without bookings all the time. The constraint had encoded an assumption nobody checked.
Sazinga
Five visitors took the site down for four hours, and the database was idle throughout
An application calling its own API by public hostname consumed two workers per request. At five workers, five simultaneous visitors deadlocked it permanently.
Sazinga
The soft delete was the bug, not the safety net
Keeping a husk row for the audit trail produced phantom drivers on eighteen legs. Deleting the row and logging the change was the safer design.
Sazinga
Trips completed this month" actually meant "assigned this month
A driver dashboard counted work by a row's updated timestamp. The timestamp was stamped on insert and had never moved on any of 221 rows.
Sazinga
The same extension was charged twice, because a mirrored total has no memory
A counter charge and an upstream re-price added the same 1,593 rupees an hour apart. Both stood, and the ledger held back the customer's deposit for it.
Sazinga
Two payouts that look identical on a bank statement and must never share a table
A co-investor's profit share and an agency's introduction commission are both money out to a company. Everything else about them differs.
Sazinga
What Generative Engine Optimisation actually is, and what makes a page citable
GEO is about being quotable by an answer engine rather than ranked by a search engine, and the two goals reward different things.
Sazinga
Stop selling the same billboard twice
Why availability derived from live bookings prevents double-selling in asset businesses, and a spreadsheet inventory structurally cannot.
Sazinga
Offline is a contract, not a feature
Designing field apps for staff with no signal: local-first writes, durable queues, idempotency and conflict rules decided by the business.
Sazinga
AI in the delivery loop, described honestly
Where AI genuinely speeds up software delivery, where it quietly costs more than it saves, and why review discipline must not loosen.
Sazinga
Why made-to-order manufacturers live in Excel, and what a pricing engine changes
Bespoke manufacturers price in spreadsheets for good reasons. A governed pricing engine keeps the flexibility and removes the drift.
Get in touch
Tell us what you are trying to fix and we will tell you honestly whether one of the applications fits, or whether this is a build.