Sazinga
Refund approval process: 245 bookings no one could open
A sign-off before refunds only works if someone holds the role to approve it. How to check yours, and what 245 stuck bookings showed us at one hire business.
Latest writing
Sazinga
A sign-off before refunds only works if someone holds the role to approve it. How to check yours, and what 245 stuck bookings showed us at one hire business.
Sazinga
A job assigned to a field worker can vanish from the supervisor's board when the list defaults to the viewer's own jobs. How to check yours, and the fix.
Sazinga
A new user with no access assigned saw everything because the system read an empty list as unrestricted. How to check yours, and what the fix was.
Sazinga
After you delete a record, adding a new one can fail because the deleted row still holds its unique code. How to check yours, and how we fixed it.
Sazinga
A manager who should see 33 people could export 15,452 rows because the limit covered only part of the report. How to check yours and how we closed it.
Sazinga
Edit opened a blank form that saved a second order, and changing a completed order risked wiping shipped quantities. How to check your system.
Sazinga
Our quotation table showed four of eight columns on a phone and the usual check passed. How to spot a table that is not responsive on mobile, and how we fixed it.
Sazinga
An employee with 404 attendance records was missing from the depot report because he was not on the staff-depot list. How to check yours.
Sazinga
A region notice reached 11 of 500 people because two region lists shared one name. How to test yours, and what is still open.
Sazinga
What proof of display to collect for lit, unlit and LED billboards: night photos only for lit boards, video for screens. What went wrong and the fix.
Sazinga
A monthly farmer-meeting programme stood at 9.2 per cent with its window closing, and no screen showed it. How to see yours while there is time.
Sazinga
Leavers still show in team screens and sales reports when offboarding removes them from one record but not the other. How to check, and what the fix took.
Sazinga
When someone covers a client's billboard, your contract and your records decide who pays for the lost display days. What to settle and record before it happens.
Sazinga
Relabelling a handover photo deleted the photo that held the label, and the next click failed six times in a row. How to check your own photo tagging.
Sazinga
An app told users to check their wifi when the network was fine: our own timeouts were shorter than the work. How to tell, and what we changed.
Sazinga
17 per cent of live employees had no manager recorded, so an AI assistant said a real colleague was not in the team. The check, and why names stay out of the index.
Sazinga
An AI assistant said nothing new was waiting while four requests sat unanswered. Tool descriptions and a date filter hid them. How to test your own.
Sazinga
An audit trail held nothing for ID, bank and odometer changes, and none for 1,231 vehicle documents. Two silent faults, and how to test your own log.
Sazinga
A field app's camera button did nothing because two permission faults hid behind swallowed errors. What to check on your own app, and what we fixed.
Sazinga
A digital screen refused every booking because a blank slot count was read as zero. What to check in your own booking system, and what we fixed.
Sazinga
Half of recent hire bookings showed documents missing in the driver app when the office had them. One rule lived in three places and they disagreed.
Sazinga
A field task list that keeps every missed check becomes a backlog nobody reads. Show one list of checks due now, and keep the full record for reports.
Sazinga
A nightly job closed rentals past their dates while cars were still out, leaving a booking that said collect and settled at once. How to check yours.
Sazinga
A partner who paid a shared bill was never repaid at settlement. How to split shared costs fairly, with a worked example, and what our fix left open.
Sazinga
We asked two AI image models for a pizza with three of eight slices left. The dearer one drew a perfect 3/8 over a whole pizza. How to choose and check.
Sazinga
A campaign report printed the close-up in the wide-shot slot because one field did three jobs. What to check in your reports, and what we changed.
Sazinga
Proof photos dated when they reached the server are wrong by days, and a rule meant to confirm location was not running. What to check, and what we fixed.
Sazinga
A kids' rewards app paid points for every retake of the same quiz. Pay for the work, not the request: how to design rewards that cannot be farmed.
Sazinga
Two Excel files and a database disagreed on 34 of 47 board locations, with no site code to join them. How to reconcile them safely, and what we did.
Sazinga
On release day 17 staff ended their shift by accident and could not start another. The fix reached every phone without a new app release.
Sazinga
A WordPress login that says cookies are blocked at random often means a cache keeping the wrong page. Ours also showed an admin's page to the public.
Sazinga
Before switching on automated booking messages, we checked what customers are told. Twenty-nine finished trips would have got a cancellation notice.
Sazinga
A three-month billboard quote came out at one month's price because the total ignored duration. How to price a multi-month booking, and what we fixed.
Sazinga
Field staff who never end their shift leave blank hours in the attendance export. Why that happens, and the reminders we set up to catch it.
Sazinga
Cancelled bookings stayed on the office board and drivers' phones, and swapped cars never reached the driver. Why booking sync misses them, and how to check.
Sazinga
An unpaid cloud bill withdrew the network while the console showed the server healthy. Why dashboards stay green, and who should receive the notice.
Sazinga
Drivers saw the office number or none at all because two faults stacked: a privacy rule and a sync that stopped linking customers. What to check.
Sazinga
A booking scheme told a dealer it had closed on its last day because the end date was compared as text. How to check yours and what we fixed.
Sazinga
Sending every broken link to the homepage creates soft 404s: endless identical pages that look real. The cause, how to check your site, and the one-line fix.
Sazinga
An AI assistant listed four requests a child never made, though told not to invent. Why it happens and the rule that stops it.
Sazinga
Handover photos from a rental inspection app arrived as a corner of the car. Large phone photos were being cut, not shrunk. How to check yours.
Sazinga
Hiding the invoice module can zero partner shares and agent commission when they are worked out from invoices. What to check first, and what we did.
Sazinga
A legal register reads as confident after the law beneath it is replaced. How to keep one current, and what happened to our 184-obligation register.
Sazinga
Field staff could read what every client was charged because removing a permission from a role revoked nothing. How to restrict pricing, and the fix.
Sazinga
A dealer at one depot could order a product and the next could not. A product shows only if four conditions hold, and failing one hides it silently.
Sazinga
A Tally link reported success while 87 of 208 customers were dropped and 10 KG arrived as 10 GM. What to check on your accounting software integration.
Sazinga
A board showed 50 jobs in queues of 100 and 95, hid the oldest, and two columns were always empty. How to check whether your dashboard tells the truth.
Sazinga
Every booking confirmation to a Gmail address was refused from one afternoon. About 37 went unconfirmed and no code had changed. How to find the cause.
Sazinga
A WhatsApp greeting told a customer to bring 18,725 rupees when the screen said 23,725. Three faults, one of them the last booking's leftovers.
Sazinga
The office changed a booking's pickup place. The portal overwrote its copy, told nobody, and the driver went to the old address. How to check yours.
Sazinga
Staff saw error pages in bursts while the server looked healthy. A customer's browser pass was crashing the portal, which restarted 340 times.
Sazinga
A product screen repeated each crop 36 times and took 2.5 seconds to open, because a table held every combination. How to check yours for duplicates.
Sazinga
A 20-site proposal deck weighed about 90 MB because every photo went in at full camera size. How to shrink one, and how we fixed it in AdBoard.
Sazinga
A rep left and his pending orders could not be approved by his manager. 143 of 1,170 were stuck the same way. How to reassign approvals safely.
Sazinga
A server security update broke a quoting system and no alert fired. How to find out first: what to ask your supplier to check after any security change.
Sazinga
A website inbox of identical emails looked like spam but held about ten real enquiries a day. How to stop form spam without losing genuine ones.
Sazinga
Thirty handover photos were taken in the app and one reached the office, with no warning on screen. Completing the job before the photos were ready caused it.
Sazinga
The portal said a number was in use though no one had it. Blank accounts made at login held it, and a stray space locked an employee out. How to check.
Sazinga
Retiring a server saved about $4 a month, not $52, because a new server, address and metered transfer took its place. How to find where your bill went.
Sazinga
Foreign phone numbers were cut to ten digits and given an Indian prefix, so a UK customer's booking reached a stranger. How to check your own numbers.
Sazinga
Old pages still showing after a relaunch usually means the old addresses return not found, not a redirect. One missing slash did it to us. How to check yours.
Sazinga
A CMS lets a page with no meta description publish. A typed content schema fails the build instead. How that works, and what it costs your editors.
Sazinga
A WordPress site keeps getting hacked when attackers can still write to the server. What stopped it for us, and how to decide what will stop it for you.
Sazinga
A new site can look perfect and still tell Google to forget it: a do-not-index tag, dead old addresses, no links between pages. What to ask whoever built yours.
Sazinga
Any signed-in rep could write any target, and 866 of 877 were in the wrong units. How to set and lock sales targets, and the checks an owner can make this week.
Sazinga
A noindex tag can sit on every page of a new site with no error, and Google then drops it. How it happens, the file-level check that catches it, and what to ask.
Sazinga
If staff can ask an AI about company data, what stops it answering the wrong person? Not a sentence telling it to behave. Where the refusal has to live.
Sazinga
9,300 of 753,994 contacts held unusable phone numbers because validation tested only one end. How we counted them, fixed them, and how to check yours.
Sazinga
ChatGPT can describe the company you used to be. Old addresses and vague pages are the usual causes. How to check what assistants say, and what to fix.
Sazinga
Reps could not start their shift though nothing was down. A slow Google lookup sat inside the request that had to succeed. How to check yours.
Sazinga
What it costs to let a sales team question their own data in plain English, why the model never produces the number, and the two defects still open.
Sazinga
A rebuilt website still brought no enquiries because the cause was demand and content, not the framework. How to find out what your site really does first.
Sazinga
An AI chatbot over company data guesses wherever the database hides how records connect. 2,667 approved orders would have been reported as cancelled.
Sazinga
Can a quote produce the cutting list and bill of materials without retyping the job? Yes, if it keeps its working. What you get, and what it cannot do.
Sazinga
GST on transport and installation in a fabrication quote: when they sit inside the taxable amount, CGST and SGST versus IGST, and what the quote must carry.
Sazinga
How to price a six-foot stainless steel work table: sheet weight, tube, labour and margin, every figure shown. Rates are from a demonstration catalogue.
Sazinga
Margin on selling and markup on cost are not the same twenty per cent. The difference, a conversion table, and what the confusion costs over a year.
Sazinga
SS 304 vs 316 vs 202 for fabricators: what differs in the metal, where each grade belongs, and a 90 per cent price spread on one identical table.
Sazinga
Most quoting software assumes a catalogue. Made-to-order fabrication needs prices computed from size, grade and your own rules. Six tests to run on any demo.
Sazinga
Why a quoting spreadsheet produces wrong prices: copied files, stale rates, hidden assumptions, margin on the wrong base. A test to run and what fixes it.
Sazinga
No hoarding size is standard in India, but 20x10, 30x10, 40x20 and 60x20 feet are common. Unipole, gantry and kiosk sizes explained, and what to record.
Sazinga
How to start a billboard business in India: owner or agency, where sites and permissions come from, and the three numbers that decide if it pays.
Sazinga
Card rate is the published price, net rate is what you accept, and commission depends on which figure it applies to. How each works in outdoor advertising.
Sazinga
Billboard management software sells physical space; digital signage software plays video. The eight things it must do, and questions to ask a vendor.
Sazinga
Empty billboard days are the largest cost nobody counts. How to work out what your vacant days cost, using one site and its monthly rate.
Sazinga
Billboard double booking is almost always a hold nobody confirmed. How it happens, and what stops it: one calendar, derived availability, expiring holds.
Sazinga
Proof of posting goes missing because photos sit in chat groups with no place, date or campaign. What good proof needs, and how to answer a client fast.
Sazinga
Outdoor advertising proposals are lost on speed and completeness, not rate. What belongs in one, and how to build it in minutes, not an evening.
Sazinga
Billboard advertising in India runs from about ₹15,000 to over ₹10,00,000 a month per face. The five things that set the rate, and rough bands by format.
Sazinga
Payments stall when the invoice, purchase order and booking disagree on dates, sites or tax. Where the mismatch starts, and how to remove it.
Sazinga
Can customers see a 3D picture before accepting a made-to-order quote? Yes, if it is drawn from the quote's own sizes. How ours works and what it leaves out.
Sazinga
A database migration can pass every test and still fail in production when development runs a newer database version. How we caught it, and what to check.
Sazinga
A pairing code is a credential, not an ID: short-lived, single-use, revocable, stored hashed. What that meant for pairing a child's tablet, and what to ask.
Sazinga
Reps see the wrong currency or dates when an app has them written into its code. Why that happens, how to check yours, and what we changed.
Sazinga
Invoice numbers get gaps when a draft takes a number and is then abandoned. How to check yours, and how we number at the moment of issue instead.
Sazinga
A portal asked for one customer's prices and got everyone's, because the server ignored the request. How to check yours, and how we closed it.
Sazinga
Python can strip every assert from a production build, and the guard with it. How we caught a login endpoint fenced off by one, and what to ask your team.
Sazinga
Staff read raw error codes when the server sends codes the screens have no wording for, and nothing flags it. Why it happens and the check that does.
Sazinga
Staff certificate portals often check what a user may do, not whose records. How to test your own software, and what we found in one system we audited.
Sazinga
A no-login quote link can show costs the PDF never would if it is built separately. The cause, the check to run before you send one, and what happened to ours.
Sazinga
A compliance register is a rule that produces a list of obligations, not a tick-list. What it should hold beyond certificates, from a register of 184 obligations.
Sazinga
A compliance dashboard percentage can come from a table nothing updates. How to check where the figure comes from, and what we found in one product.
Sazinga
Tests failing when nobody changed the code usually means a shared test environment filled up. How we found it, and how to check yours.
Sazinga
In one training records system a worker closed a compliance gap by uploading any file, before a manager looked. How to test yours and what to ask.
Sazinga
In PostgreSQL a view runs as its owner, so it can ignore row-level security and sum every customer's data. How we caught it before launch, and what to ask.
Sazinga
Can you use AI on your pricing without sending it to an outside provider? Only if it runs on your own machine. The design rules we set, and what is still unproven.
Sazinga
A module reported complete could not be used by a rep in a shop, and real progress was about half the tracker's. How to check progress yourself.
Sazinga
How to check that a spreadsheet-to-software move lost nothing. Ours imported clean and was still 102 rules short. The count-by-count test that found them.
Sazinga
When a tax portal is slow or down, a till built the obvious way freezes. How e-invoicing should work at the counter, and what to ask your supplier.
Sazinga
An auditor asks what a record said in March and who changed it. A rule staff follow is a promise; a database that refuses edits is evidence.
Sazinga
A clerk who could only upload spreadsheets created customers and products she could not add by hand. How to check yours, and why one bad row stops uploads.
Sazinga
Pricing in inches, customer wants millimetres. Keep one unit inside and convert at the edge. The other two designs corrupt old quotes, and how we nearly missed one.
Sazinga
A mobile app worked for weeks in development and failed on its first release build. Development mode never ran the code paths that broke. What to check.
Sazinga
An AI quiz generator put the right answer in the same position on a hundred and fifty questions. Each was correct; the set was broken. How to check yours.
Sazinga
How to price a product when one part's price depends on its size. Thirteen of 362 rules needed it; the usual nested IF in one cell was readable by one person.
Sazinga
In a fabrication business the person who quotes is often the owner or their son, working from a phone. How we found that, and why setup-heavy screens go unused.
Sazinga
Yes: a client generated from a schema copies what the schema states and guesses the rest. Ours guessed one credential pair backwards. How to catch it.
Sazinga
An AI chat reply hit its length limit mid-draft and its control text reached the screen. Why replies get cut off, and what to check in your own AI feature.
Sazinga
A build report said passing because it carried the exit code of the last command in a pipeline. How it happens, and what to ask when a report says tests pass.
Sazinga
A till refused to bill because invoice numbers came from a clock and repeated every 16 minutes across customers. Causes, and how to check yours.
Sazinga
A tunnel made the live database answer on localhost, so a day of migrations ran against production. How it happens, and the checks that stop it.
Sazinga
If signing out only clears the screen, a copied login stays valid for hours. A real case, eight hours, plus what to check and what has to change on the server.
Sazinga
Every contract bug in a 57-screen rebuild sat between contributors. Generating the interface from the server turned those disagreements into build failures.
Sazinga
A low-stock screen showed nothing while stock ran down, because no item had a reorder level. Why blank is not zero, and how to check yours.
Sazinga
Nine kinds of alert were sent and none reached a phone, because no phone had registered an address. Why app notifications fail silently, and what to check.
Sazinga
How long to move a pricing spreadsheet into quoting software? For us, weeks of developer time, because the self-service importer is not built.
Sazinga
Without a staging environment, defects are found on your real records. What to ask your supplier, and how one test suite gated the push and checked the deploy.
Sazinga
Valid orders showed as rejected by the office after a server restart, because the app could not tell a failed connection from a refusal. How to check yours.
Sazinga
How to price a made-to-order product with many variants: price each feature once, not each product. 24 features and 62 variants became workable.
Sazinga
What auditing a fabricator's quoting spreadsheet found: twelve formulas referenced but never defined, with a person quietly patching the gaps.
Sazinga
Our new system priced every item right yet nobody would send the quotation. What a professional quotation format needs: grouping, line keys, specification lines.
Sazinga
An audit log hid the request but stored old and new passwords in clear, then showed a password change as no change. How to check your own log.
Sazinga
Removing a child from an app left her tablet signed in, because removal only hid the record. How to check your own system, and what the fix was.
Sazinga
A quote that shows only the price hides your margin. Running the same pricing rules on selling and cost rates gives the profit on every feature of every job.
Sazinga
Stock software that gives each location one type forces paper transfers inside one building. Describe a site by what it can do instead.
Sazinga
A lesson app showed a child one question of seven. A repeated create step and an unordered query combined, with no error. What to ask, and what we fixed.
Sazinga
Retiring a product left orphaned prices and variants. Settings and totals follow the product; records of what happened never do. How to retire one safely.
Sazinga
A customer asks why a quote came to that price weeks later, and rates have moved. Storing the working lets you show the breakdown; keeping only the total cannot.
Sazinga
A project status list said a feature was not built, so two rounds of work were commissioned. It had shipped. How to trust a status report, and what we changed.
Sazinga
Systems that refuse to receive more than the purchase order push clerks to edit the order. Handle over-delivery with a flag, tolerance or approval.
Sazinga
A POS rule skipped for account owners let a sale be booked from a store with no till. How POS stock rules go wrong, and how to test yours.
Sazinga
A compliance dashboard guessed the unit of a stored score, so a true 1 per cent showed as 100. How that happens and how to check your own.
Sazinga
A certificate expiring today was on no dashboard list because three rules treated the boundary differently. How expiry tracking should work, and a test.
Sazinga
A deploy printed Done but never restarted the app, so the old version kept serving for weeks. How to check what is really running, and what we fixed.
Sazinga
Can quoting software read sizes off shop drawings? All 14 of ours were stamped not to scale. What a drawing can and cannot tell a quote.
Sazinga
Stock was taken off at order and again at dispatch, and partial dispatch let two drops ship the last unit. How to check why your stock count is wrong.
Sazinga
A model-not-found 404 hit every fresh API key while our own key worked. Availability is per account. What to check before you ship an AI feature.
Sazinga
Hundreds of pricing formulas to check and the review stalled. Sample prices, a flagged shortlist and a separate human sign-off are what finish it.
Sazinga
A quiz score cannot show a lesson was read, least of all on safety. What our app could and could not record, and how to question your own training.
Sazinga
Our system said 1,081 prices were missing while every quote was correct. About 33 were real. How to tell which price list warnings to trust.
Sazinga
A plan and a database said an app was largely built; about forty per cent had no server behind it. How to audit an unfinished project before you pay.
Sazinga
When a trial expires or a card fails, software can lock the customer out with no warning and no way to undo it. What to check, and what we found.
Sazinga
Two tills sold the last case and stock fell once because three code paths changed stock three ways. How to find why your stock does not match.
Sazinga
TRUNCATE CASCADE empties every table linked by a foreign key, including rows unrelated to what you cleared. Here it wiped every role and permission.
Sazinga
A children's learning app returned twelve questions when fifteen were asked and said nothing. Three ways to handle a short result, and the one we chose.
Sazinga
A published lesson showed an empty list on the child's tablet because publishing and assigning were separate steps. How to check, and how we fixed it.
Sazinga
Why changing the steel grade changes more than the sheet price in a quote: sometimes only the rate changes, sometimes the calculation does. How to handle both.
Sazinga
A driver with no signal got a spinner, not a delivery form. Offline capture existed but could not be reached. What should work offline, and what should not.
Sazinga
Yield recorded per batch hides a bad pass. Record output per run to see which pass loses product, and expect the report to start from a date.
Sazinga
Field staff on poor signal can lose records or get the same ones on every refresh. A timestamp cursor is the usual cause. What to ask your supplier.
Sazinga
Invoicing software can charge 18% on a zero-rated sale because it reads a zero rate as no rate. How to test yours and what to ask your supplier.
Sazinga
An AI feature failed half the time and blamed the network, but one supplier's blank success stopped the fallback chain. What to check in your own.
Sazinga
Removing a driver from a booking worked on one screen and silently did nothing on another. The cause, what it cost the audit trail, and how to test yours.
Sazinga
A rental app read a pending deposit as money received and told the driver nothing was owed. Why it happens, and an afternoon check to find it in your system.
Sazinga
A driver app said 86 jobs were open this month and three were. A status only one action can change drifts from the truth. How to check your own count.
Sazinga
Tests can pass while the feature is broken, because the check was never able to fail. Examples from our own work, and how to test your supplier's tests.
Sazinga
When someone denies changing fifty accounts, only an audit trail that names the records and the person can settle it. What to check in yours.
Sazinga
Billboard availability depends on the date you are selling for, not today. A list built on today's bookings shows the wrong sites. How to check yours.
Sazinga
A promotion and free trials ended five and a half hours off because the software used UTC, not the business clock. How to check which clock yours uses.
Sazinga
Hacked again after cleanup while the scanner says clean? Scanners match appearance. Comparing every file with the official release found 211 files they missed.
Sazinga
Reusing 67,000 staff-tagged handover photos sorted new ones with no training. Damage close-ups were only 36% right, so those stay with a person.
Sazinga
To keep one customer's data from mixing with another's in a shared database, enforce it in the database, not only the app. Two designs and the gaps of each.
Sazinga
An approval step no expense could reach, because every claim was approved on creation. Three tests for what to remove before you decide to rebuild.
Sazinga
A static site has no database, login or plugins to attack. Two compromised brochure sites were rebuilt that way. When it is the right answer, and when not.
Sazinga
A receivables ledger kept in its own table drifts from the invoices after every payment. How to check yours, and why we worked the figure out instead.
Sazinga
Software feels scattered when its menus follow data types and your work follows a process. What to check before you choose workflow management software.
Sazinga
Can a pricing system let the business own its formulas without a developer? 362 formulas live outside the code. What to check before you choose one.
Sazinga
Building every client pitch deck by hand means retyping what the booking already holds. How to check yours, and how we generated the deck and cost sheet.
Sazinga
A child was paid points twice for one task and nobody could say why. Why a stored total can't be trusted, and how a ledger of entries fixes it.
Sazinga
One card payment was credited twice because two messages arrived 434 milliseconds apart, then the customer was asked for the deposit again. Cause and checks.
Sazinga
A dashboard showing zero owed above a list of unpaid invoices is adding text, not money. How to check your total, and the fix.
Sazinga
A digital screen loops six to eight adverts, but software built for painted boards allows one. How slots should be booked, and what to check.
Sazinga
One site was hacked and every site on the server fell because they shared a database password. How to check yours, and the order to fix it in.
Sazinga
Several websites ran as one user on one server, so one hack reached all. How to check your hosting, and what separating the sites changed.
Sazinga
Nine screens worked out the driver in nine ways: 81 legs got an arbitrary answer, 16 the wrong name, 17 a phantom. What we changed and how to check yours.
Sazinga
A booking with no end date breaks availability if the date is left blank. How to record a rolling contract so every date question still works.
Sazinga
Can staff ask a business system questions in plain English without seeing what they should not? Yes, if limits sit in what it can reach. What to check.
Sazinga
Two hard-coded roles make everyone an administrator. Why roles should be built from fine-grained permissions, and how 77 permissions replaced them.
Sazinga
Software stops after each step when records are stored but not linked forward. What to check in your own system, and how we fixed it in AdBoard.
Sazinga
Every screen limited a branch manager to one branch, but the export did not. How to check what your staff can download, and what closing the gap took.
Sazinga
A customer paid the rental and a five thousand rupee deposit online, then was asked for five thousand more. Why the expected deposit read ten thousand.
Sazinga
Orders taken without signal showed as failed though saved, or vanished from the phone though refused. How to test your own order taking app, and what we fixed.
Sazinga
A nightly database backup wrote nothing for four days with no alert. Why failed backups go unnoticed, and how to check yours in under a minute.
Sazinga
A booking system checked clashes on one site, not all four faces of the campaign. How to test yours for the same gap, and what we changed to close it.
Sazinga
Staff saw a record in the list, then got not found on opening it, because a branch check compared two different kinds of value. How to find and fix yours.
Sazinga
Software that insists on a booking cannot record an advance, a credit, or a partner's or supplier's bill. What to check, and how we relaxed the rule.
Sazinga
A booking site went down for four hours with hardly any visitors and an idle database. Why a bigger server would not have helped, and how to tell busy from blocked.
Sazinga
Eighteen trips still showed a driver who had been removed, and seven lost the removed driver's identity. Why a soft delete caused it, and what to check.
Sazinga
A driver dashboard counted trips by an updated timestamp that never moved on any of 221 rows, so completed meant assigned. How to check your own counts.
Sazinga
A counter charge and an upstream re-price both added 1,593 rupees an hour apart, and the ledger held back the customer's deposit. Why, and how to check.
Sazinga
A partner's profit share and an agent's commission both go out monthly but differ in basis, period and scope. Why they must never be totalled together.
Sazinga
Generative engine optimisation is the engineering of what a site serves to AI assistants, so they describe you correctly. What they read, and what we fixed.
Sazinga
Outdoor advertising software stops double booking when availability is worked out from live bookings, not typed into a status column. What to check.
Sazinga
Orders vanish or double when a field sales app loses signal. Three decisions to settle in writing before you commission or buy an offline sales app.
Sazinga
Where AI genuinely speeds up building software, where it quietly costs you more, and the one review rule a supplier should never loosen.
Sazinga
Made-to-order manufacturers price in Excel because the rule owner can edit it. What goes wrong with copies and rates, and what a governed engine replaces it with.
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.