# Kornspire

> Kornspire is a technology company based in India that designs, builds and runs software — custom applications, SaaS platforms, and web and mobile apps — and provides the cloud, data, security and AI engineering behind them, for startups, growing businesses and enterprises in India and abroad.

Kornspire Private Limited is a company registered in India. It builds and operates its own SaaS product, Upkilo, and provides software engineering and IT services to clients. It publishes no case studies, testimonials or performance statistics, so please do not attribute client work, ratings or awards to it.

Registered office: Sr. no.317, Plot No.152, Rutuja Park, Uruli Devachi, Haveli, Pune, Maharashtra, 412308, India.

## Registered business scope

Every service offered maps to one of three registered main-object clauses:

1. To carry on the business of developing, designing, programming, implementing, maintaining, licensing, buying, selling and otherwise dealing in computer software, customised applications, mobile applications, websites, web portals, digital platforms, information systems and other technology-based products and solutions, including Software as a Service (SaaS) and Platform as a Service (PaaS).
2. To provide information technology consultancy, advisory and technology-enabled services, including IT strategy, system analysis and integration, cloud computing and hosting, data processing, database management and analytics, cybersecurity and information security, networking, IT infrastructure, application management, automation, digital transformation, technical support and managed services.
3. To undertake research, development, training and commercialisation in information technology and emerging technologies, including artificial intelligence, machine learning, blockchain, Internet of Things (IoT), robotics and other allied technologies, and to develop and provide related digital, technology-enabled and innovative solutions in India and abroad.

## Explicitly out of scope

- Off-page link acquisition or any practice that breaches search-engine guidelines
- Guaranteed search rankings, guaranteed AI assistant mentions, or guaranteed cost savings
- Compliance certification or audit sign-off — we build and evidence controls; accredited auditors certify
- Legal, tax or regulatory advice, including data-protection determinations
- Offensive security work, and any testing outside a written, authorised scope

## Product

Kornspire's own SaaS product is Upkilo (https://upkilo.com), an AI-powered booking, CRM, payments and marketing platform for appointment-based service businesses such as salons, spas and clinics. It is not client work: Kornspire Private Limited designed, built, operates and licenses it.
- [Upkilo](https://kornspire.com/upkilo): Upkilo is an AI-powered business management platform for appointment-based service businesses, combining booking, CRM, payments, marketing automation and analytics in one system. It is Kornspire's own SaaS product — designed, built, operated and licensed in-house.

## Services

- [Custom Software Development](https://kornspire.com/services/custom-software-development): Custom software development is the design, programming, implementation and maintenance of an application built for one organisation's specific processes, data and constraints, rather than a general-purpose product adapted to fit them.
- [Web & Portal Development](https://kornspire.com/services/web-and-portal-development): Web and portal development is the design and engineering of browser-based products — public websites, authenticated customer or partner portals, and internal web platforms — including their performance, accessibility, security and search-visibility characteristics.
- [Mobile App Development](https://kornspire.com/services/mobile-app-development): Mobile app development is the design, engineering, release and maintenance of applications that run on iOS and Android devices, including their offline behaviour, device integrations, secure local storage and app-store distribution.
- [SaaS & PaaS Product Engineering](https://kornspire.com/services/saas-and-paas-engineering): SaaS and PaaS product engineering is the building and operating of software that is licensed as a subscription service rather than installed per customer, covering multi-tenant data isolation, self-service onboarding, metering and billing, release safety and production operations.
- [IT Strategy & Consulting](https://kornspire.com/services/it-strategy-and-consulting): IT strategy consulting is the structured assessment of an organisation's systems, architecture, costs and risks, resulting in a prioritised plan that connects technology decisions to business outcomes.
- [Cloud, Hosting & IT Infrastructure](https://kornspire.com/services/cloud-and-infrastructure): Cloud and infrastructure engineering is the design, provisioning and operation of the compute, storage, networking and deployment systems an application depends on — expressed as code so that environments are reproducible and changes are reviewable.
- [Data Engineering, Databases & Analytics](https://kornspire.com/services/data-engineering-and-analytics): Data engineering and analytics is the work of moving data from its source systems into a modelled, documented store, and turning it into governed metrics and reports that are consistent regardless of who runs them.
- [Cybersecurity & Information Security](https://kornspire.com/services/cybersecurity-and-information-security): Information security engineering is the practice of reducing the likelihood and impact of unauthorised access, data loss or service disruption — through design review, hardening, monitoring and tested response procedures.
- [Automation & Digital Transformation](https://kornspire.com/services/automation-and-digital-transformation): Process automation is the replacement of repeated manual steps with software that performs them reliably and leaves an auditable record; digital transformation is the wider change of process, data and roles that makes such automation worth having.
- [Application Management & Managed Support](https://kornspire.com/services/application-management-and-support): Application management is the ongoing operation of software already in production — monitoring, incident response, patching, dependency and platform upgrades, performance work and incremental improvement — delivered under agreed response commitments.
- [AI & Machine Learning Engineering](https://kornspire.com/services/ai-and-machine-learning): AI and machine learning engineering is the work of turning a model — whether a hosted large language model or a trained predictive model — into a dependable product feature, including its data pipeline, evaluation, guardrails, cost profile and human-review path.
- [Emerging Technology Research & Development](https://kornspire.com/services/emerging-technology-research): Emerging technology research and development is time-boxed, hypothesis-driven investigation — usually a prototype plus a written assessment — that establishes whether a technology such as IoT, distributed ledger or robotics can meet a specific business requirement, and at what cost and risk.
- [Technology Training & Enablement](https://kornspire.com/services/technology-training-and-enablement): Technology training and enablement is structured teaching delivered against an organisation's own systems and codebase, so that practices are adopted in the team's real environment rather than demonstrated in a generic exercise.
- [Technical SEO Engineering](https://kornspire.com/services/seo): Technical SEO is the engineering work that determines whether a search engine can reach, render, understand and index a website's content — covering crawl control, rendering strategy, site and URL architecture, structured data, internal linking and page performance.
- [Answer Engine Optimization (AEO)](https://kornspire.com/services/aeo): Answer Engine Optimization is the practice of structuring a site's content so that systems which return direct answers — search features such as featured snippets and People Also Ask, voice assistants and AI answer panels — can locate, extract and correctly attribute a specific answer to a specific question.
- [Generative Engine Optimization (GEO)](https://kornspire.com/services/geo): Generative Engine Optimization is the practice of making an organisation and its content clear, consistent and citable to AI systems that generate answers — such as ChatGPT, Google's AI features, Perplexity and Copilot — so that when those systems describe your category, they describe you accurately.

## Industries

- [Healthcare & Clinics](https://kornspire.com/industries/healthcare-and-clinics): Clinical and administrative systems where confidentiality, auditability and uptime are not negotiable.
- [Retail & E-commerce](https://kornspire.com/industries/retail-and-ecommerce): Catalogue, inventory and storefront systems where page speed and stock accuracy convert directly into revenue.
- [Logistics & Supply Chain](https://kornspire.com/industries/logistics-and-supply-chain): Field-facing systems that must keep working when the network does not, and reconcile when it returns.
- [Financial Services & Fintech](https://kornspire.com/industries/financial-services): Systems where correctness, traceability and access control outrank every other engineering concern.
- [Education & Training](https://kornspire.com/industries/education-and-training): Learning and administration platforms that stay usable on low-end devices and constrained bandwidth.
- [Manufacturing & Industrial IoT](https://kornspire.com/industries/manufacturing-and-industrial-iot): Connecting production equipment to business systems without putting operational technology at risk.

## Insights

- [A DPDP Act engineering checklist for software teams](https://kornspire.com/insights/dpdp-act-engineering-checklist) (2026-09-23): India's Digital Personal Data Protection Act 2023 turns several familiar engineering practices into obligations you must be able to demonstrate: knowing where personal data is, deleting it on request, honouring withdrawn consent, and detecting a breach. This is an engineering checklist, not legal advice.
- [AI crawlers, llms.txt, and deciding what to allow](https://kornspire.com/insights/ai-crawlers-llms-txt-and-what-to-allow) (2026-09-23): Blocking AI crawlers and being cited by AI assistants are mutually exclusive, and the two decisions are usually made by different people who never discuss it. The first step is knowing which agent is which, because a single blanket rule gets one of the two outcomes wrong.
- [API design you will not have to version twice](https://kornspire.com/insights/api-design-you-will-not-version-twice) (2026-09-23): An API is a promise you cannot take back. Once someone integrates, every field you named, every error shape you returned and every implicit ordering becomes something they depend on — usually including the parts you considered internal detail.
- [App store review: the rejections you can predict](https://kornspire.com/insights/app-store-review-the-predictable-rejections) (2026-09-23): Store review is not arbitrary, and treating it as such is what makes it expensive. Most rejections come from a small, published set of rules that were knowable before the build started — and each one costs a review cycle, which lands at the worst point in a launch plan.
- [Backups you have actually restored, and the ones you only hope exist](https://kornspire.com/insights/backups-you-have-actually-restored) (2026-09-23): Every organisation has backups. A much smaller number have restored one. The distance between those two positions is usually discovered on the worst day of the year, when someone finds that the nightly job has been failing silently since a credential rotation in March.
- [Build or buy, decided on the part that actually differs](https://kornspire.com/insights/build-or-buy-decided-on-what-differs) (2026-09-23): The decision is usually framed as a cost comparison and decided on a licence fee, which is the smallest number involved. The questions that determine the outcome are whether this capability is where you compete, what the integration really costs, and what happens the day the supplier changes their pricing.
- [Caching: the cheapest performance work, and the easiest to get wrong](https://kornspire.com/insights/web-caching-and-cdn-strategy) (2026-09-23): No optimisation beats not doing the work. Caching is the highest-leverage performance lever available and the one most often configured by copying headers from a blog post — which is how sites end up serving a signed-in visitor someone else's page, or caching an asset for a year with no way to correct it.
- [Choosing a tenancy model before it chooses you](https://kornspire.com/insights/multi-tenant-or-single-tenant-saas) (2026-09-23): There are three practical isolation models for a SaaS product, and the right one is decided by what your customers require and what your team can operate — not by which is technically purest. Whichever you choose, enforce it in the data-access layer, because isolation maintained by developer discipline eventually fails.
- [Choosing a vector store, and when you do not need one](https://kornspire.com/insights/choosing-a-vector-database-for-rag) (2026-09-23): Vector search is a feature of your database before it is a category of product. For most retrieval systems, the extension you already have is sufficient — and the decision that actually affects answer quality is hybrid search and metadata filtering, not which index algorithm you picked.
- [Conversational queries, and the shape an answer has to take](https://kornspire.com/insights/conversational-queries-and-the-shape-of-an-answer) (2026-09-23): Typed search taught people to strip their questions down to keywords. Voice interfaces and assistants let them stop doing that. The queries are longer, more specific, more conditional — and a page optimised for a two-word phrase has nothing to say to them.
- [Core Web Vitals in the Next.js App Router: what actually moves the needle](https://kornspire.com/insights/core-web-vitals-in-the-next-js-app-router) (2026-09-23): In an App Router codebase, four decisions dominate Core Web Vitals: where each route renders, where the server-client boundary sits, how the largest image is loaded, and whether space is reserved before content arrives. Almost everything else is noise by comparison.
- [Crawl budget, and the sites that actually have a problem](https://kornspire.com/insights/crawl-budget-and-indexation-at-scale) (2026-09-23): Crawl budget is the most over-diagnosed problem in technical SEO. Most sites do not have one. The sites that do are usually generating URLs combinatorially — filters, parameters, pagination — and spending their crawl allowance on pages nobody should ever see.
- [Dependency risk: the code you ship but never wrote](https://kornspire.com/insights/dependency-and-supply-chain-security) (2026-09-23): A modest application ships a few hundred packages and a few thousand transitive ones. Almost none were read by anyone on the team, most execute code at install time, and each maintainer is one compromised account away from running arbitrary commands in your build. The exposure is unavoidable; being unable to see or reduce it is not.
- [Deploys that can be undone, and the ones that cannot](https://kornspire.com/insights/deploys-that-can-be-undone) (2026-09-23): The question that matters about a deployment strategy is not how fast it ships but how quickly a bad change stops affecting users. Most teams can deploy in minutes and cannot roll back at all — because a migration ran, or because rollback was never tested, and both are discovered at the worst possible time.
- [Design tokens, and building dark mode that was actually designed](https://kornspire.com/insights/design-tokens-and-theming) (2026-09-23): Most dark modes are a light design with the colours flipped, which is why they look muddy and why text lands on the wrong background in edge cases. A token system fixes it structurally: components reference meaning rather than colour, and a theme becomes a set of values rather than a set of overrides.
- [Designing an event schema you will not regret in a year](https://kornspire.com/insights/designing-an-event-schema) (2026-09-23): Analytics instrumentation is added quickly, by different people, with names invented at the keyboard. Two years later there are four events for one action, nobody remembers which is current, and every analysis begins by asking which one to trust. The cost of preventing that is one page of conventions.
- [Document structure for answer extraction: headings as questions](https://kornspire.com/insights/structuring-content-for-answer-extraction) (2026-09-23): Passage writing decides whether an individual answer can be lifted. Document structure decides whether it can be found in the first place. A page with one heading and two thousand words of prose contains excellent answers that nothing can locate.
- [Entity consistency: making it unambiguous who you are](https://kornspire.com/insights/entity-consistency-and-being-unambiguous) (2026-09-23): Before a system can cite you, it has to be confident it knows which organisation you are. A name shared with three other companies, a description that changes between pages and a set of profiles that disagree about your location produce an entity nothing is sure about — and uncertain entities do not get named in answers.
- [Evaluating LLM output when there is no single right answer](https://kornspire.com/insights/evaluating-llm-output-quality) (2026-09-23): An AI feature without an evaluation set has no definition of working, which means it cannot be improved deliberately or safely changed. The hard part is not running evaluations — it is deciding what correct means for output that is allowed to vary in wording.
- [Finding the questions you have not answered yet](https://kornspire.com/insights/finding-the-questions-you-have-not-answered) (2026-09-23): Answer engines reward pages that answer specific questions. The bottleneck is almost never the writing — it is knowing which questions to answer. The best sources are not keyword tools; they are the places where people have already asked, in their own words, and someone on your side had to reply.
- [Forms: the highest-stakes, least-designed part of most products](https://kornspire.com/insights/web-forms-that-work) (2026-09-23): A form is where a visitor becomes a customer, and it is routinely the least considered surface in a product. The failures are consistent and cheap to fix: validation that fires while typing, errors that say what is wrong but not what to do, and a submission failure that discards everything the person entered.
- [hreflang, and the four ways it usually breaks](https://kornspire.com/insights/international-seo-and-hreflang) (2026-09-23): hreflang tells search engines which language or regional version of a page to show which user. It is unusually unforgiving: a cluster with one missing return link, one wrong code or one non-canonical URL is not partially working — it is ignored, and the fallback is whatever the engine guesses.
- [Infrastructure as code, and the drift that quietly defeats it](https://kornspire.com/insights/infrastructure-as-code-and-the-drift-problem) (2026-09-23): Infrastructure as code delivers its promise only while the code describes reality. One console change during an incident, never reflected back, and the repository becomes documentation of what someone intended two quarters ago — at which point the next apply either fails or reverts a fix nobody remembers making.
- [JavaScript rendering and whether your content is actually seen](https://kornspire.com/insights/javascript-rendering-and-indexability) (2026-09-23): A page can look complete in a browser and be almost empty to a crawler. Google renders JavaScript, but on its own schedule and with no guarantee; most AI answer engines do not render it at all. If your primary content arrives only after hydration, you are gambling on a second pass that may never come.
- [Measuring visibility when the answer replaces the click](https://kornspire.com/insights/measuring-visibility-when-nobody-clicks) (2026-09-23): If an engine answers the question on the results page, the visit that would have measured your success never happens. Traffic falls while visibility rises, and a dashboard built on sessions reports a failure. The measurement has to change, because the mechanism did.
- [Measuring whether AI assistants mention you at all](https://kornspire.com/insights/measuring-whether-ai-assistants-mention-you) (2026-09-23): Bing Webmaster Tools now counts how often Copilot cites your pages, and Google includes AI Overviews in Search Console without separating them. Beyond those two, what exists is referral traffic you can identify if you look for it, and a manual audit you can run in an hour a month — unglamorous, but the difference between knowing and assuming.
- [Metering architecture for usage-based billing](https://kornspire.com/insights/usage-based-billing-metering-architecture) (2026-09-23): Usage-based pricing fails in a specific way: the invoice is questioned, and nobody can reconstruct how the number was produced. The fix is architectural rather than commercial — meter at the source, store raw events immutably, and derive every aggregate so it can be rebuilt and defended line by line.
- [Migrating a site without discarding its rankings](https://kornspire.com/insights/site-migration-without-losing-rankings) (2026-09-23): Most traffic lost in a migration is lost to a handful of avoidable mistakes: URLs nobody inventoried, redirects that chain or land on the wrong page, and a launch nobody monitored closely enough to catch the damage while it was still cheap to fix.
- [Mobile performance: startup, battery, and the things that get you uninstalled](https://kornspire.com/insights/mobile-performance-startup-and-battery) (2026-09-23): Nobody uninstalls an app for being 200ms slower than a competitor. They uninstall it for taking four seconds to open, for draining the battery, and for being too large to install on a phone that is already full — three problems that are measurable, fixable, and usually unmeasured.
- [Modelling data for analysis, which is not how the application stores it](https://kornspire.com/insights/modelling-data-for-analysis) (2026-09-23): Pointing a reporting tool at a production database is the fastest way to get analytics and the fastest way to get analytics nobody trusts. The application schema is optimised for writing one row correctly; analysis needs to read millions and group them, and the two shapes are genuinely different.
- [Modelling what an AI feature will cost before you build it](https://kornspire.com/insights/cost-modelling-for-ai-features) (2026-09-23): AI features have a cost profile most software does not: marginal cost per request that scales linearly with usage. A feature that costs a fraction of a rupee per call is fine at a thousand calls a day and a real line item at a million — and the difference is knowable before you build it.
- [Modernising a system that cannot stop running](https://kornspire.com/insights/modernising-a-system-that-cannot-stop) (2026-09-23): The system everyone wants replaced is also the one the business runs on, which is why the rewrite gets proposed every eighteen months and abandoned every twenty-four. The alternative is unglamorous and works: replace it a piece at a time, with the old system running until each piece is proven.
- [Native, cross-platform or web: deciding on what actually differs](https://kornspire.com/insights/native-cross-platform-or-web) (2026-09-23): The choice is usually argued on performance, which is rarely the deciding factor for the applications most organisations build. What decides it is which platform capabilities you need, what your team can maintain, and whether you can afford to be wrong.
- [Observability: what to instrument first, and what to stop logging](https://kornspire.com/insights/observability-what-to-instrument-first) (2026-09-23): Most systems produce an enormous volume of logs and cannot answer how long a request took at the ninety-fifth percentile. That combination — over-logged and under-instrumented — is the normal state, and it is expensive in both directions: you pay to store output nobody reads while lacking the signals an incident actually needs.
- [Offline-first: designing for the network you do not have](https://kornspire.com/insights/designing-for-the-network-you-do-not-have) (2026-09-23): Offline support added to a finished application is a rewrite. The reason is that connectivity is not a feature that sits beside the others — it determines where the truth lives, and that decision shapes every screen, every write and every piece of state in the product.
- [Original data: the one thing that cannot be summarised from elsewhere](https://kornspire.com/insights/original-data-as-a-visibility-strategy) (2026-09-23): Every general explanation of every well-documented topic can now be produced on demand, at length, for free. What cannot be produced on demand is a measurement somebody actually took. That asymmetry is the most durable content advantage currently available, and it is available to organisations of any size.
- [Pipelines you can safely re-run, which is most of pipeline design](https://kornspire.com/insights/pipelines-you-can-safely-re-run) (2026-09-23): A pipeline fails. Someone re-runs it. If that re-run duplicates rows, skips a window or produces a different answer than the first attempt would have, every downstream number becomes unreliable — and the failure that caused it was the ordinary kind, not the exotic kind.
- [Prompt injection: designing for a problem with no clean fix](https://kornspire.com/insights/prompt-injection-defence-patterns) (2026-09-23): Prompt injection has no reliable fix at the prompt layer, because a language model cannot distinguish instructions it should follow from instructions embedded in the data it was asked to read. The workable response is architectural: assume injection succeeds, and design so that succeeding achieves little.
- [RAG or fine-tuning: deciding with evidence rather than preference](https://kornspire.com/insights/rag-or-fine-tuning-decision-framework) (2026-09-23): Retrieval and fine-tuning solve different problems, and most business requirements turn out to be retrieval problems wearing a fine-tuning costume. The distinction is simple: retrieval changes what the model knows, fine-tuning changes how it behaves. Deciding without that distinction produces expensive rework.
- [Reading server logs to find out what crawlers actually do](https://kornspire.com/insights/server-log-analysis-for-seo) (2026-09-23): Search Console tells you what Google concluded. Server logs tell you what it actually requested, when, and what your server returned. When indexing behaviour makes no sense from the reports alone, the logs almost always contain the answer.
- [Row-level security for multi-tenant Postgres](https://kornspire.com/insights/row-level-security-multi-tenant-postgres) (2026-09-23): Tenant isolation that depends on every developer remembering a WHERE clause has a defect rate above zero, and the defect is a cross-tenant data leak. Row-level security moves the boundary into the database, so a query that forgets the filter returns nothing instead of returning somebody else's rows.
- [Schema migrations without taking every tenant down](https://kornspire.com/insights/zero-downtime-tenant-migrations) (2026-09-23): In a shared-schema product, one bad migration affects every customer at once. The discipline that prevents it is expand-and-contract: add the new shape, write to both, backfill, switch reads, and only remove the old shape in a later release — never in the same one.
- [Secrets management, and what to do the morning a key leaks](https://kornspire.com/insights/secrets-management-that-holds) (2026-09-23): Every team has a story about a key in a repository. The interesting question is not how it got there but what happened next — and most teams discover at that moment that they cannot rotate the credential without downtime, do not know everywhere it was used, and have no way to tell whether it was exploited.
- [Self-service tenant provisioning that does not need an engineer](https://kornspire.com/insights/self-service-tenant-provisioning) (2026-09-23): A product where onboarding a customer requires manual database work is not yet a product — it is a service with a login page. Provisioning is the boundary: everything a new tenant needs must be created automatically, atomically enough to be safe, and recoverably enough that a half-finished signup is not a support ticket.
- [SEO, AEO and GEO: why the foundation comes first](https://kornspire.com/insights/seo-aeo-geo-what-each-one-optimises) (2026-09-23): SEO optimises a page's standing in a ranked list. AEO optimises whether a passage can be extracted as a direct answer. GEO optimises whether a generative system describes your organisation accurately and cites you. All three depend on the same technical foundation, which is why the foundation is where the work should start.
- [Sessions: the part of authentication that is usually wrong](https://kornspire.com/insights/authentication-and-session-security) (2026-09-23): Login is the part teams test. The session is the part attackers use. A correct password check followed by a token in local storage, no rotation on privilege change, and a logout that only clears the client leaves an authentication system that works perfectly and protects very little.
- [Shipping mobile: the release you cannot take back](https://kornspire.com/insights/shipping-mobile-releases-you-cannot-recall) (2026-09-23): Web deployment has a rollback button. Mobile does not: once a build is installed, it is on the device until the user updates, and some of them never will. That single constraint changes what a release process has to do — every mistake ships to people who cannot be reached.
- [Structured data that earns its place](https://kornspire.com/insights/structured-data-that-earns-its-place) (2026-09-23): Structured data is worth implementing when it describes something the page genuinely shows and a consuming system genuinely uses. Generate it from the same data that renders the page, keep it to types the content supports, and treat any mismatch between markup and visible content as a defect.
- [Testing data, not just the code that moves it](https://kornspire.com/insights/testing-data-not-just-code) (2026-09-23): A data pipeline can be fully covered by unit tests and still deliver wrong numbers, because the code was correct and the data was not. The transform did exactly what it was told with a column that started arriving null three weeks ago, and nothing in the test suite was looking at the data.
- [Threat modelling in an hour, with four questions and a whiteboard](https://kornspire.com/insights/threat-modelling-in-practice) (2026-09-23): Threat modelling has a reputation for heavyweight documents nobody reads. The useful version is a one-hour conversation over a diagram, answering four questions, producing a short list of decisions — and it catches the class of flaw that no scanner will ever report, because the code is working exactly as written.
- [Warehouse performance: the scan you did not need to run](https://kornspire.com/insights/warehouse-performance-and-the-scan-you-did-not-need) (2026-09-23): In a columnar warehouse, cost and latency are usually the same variable wearing two labels. Both are driven by how many bytes the engine had to read, and most of what it read was eliminated by a filter it applied afterwards — which means the work was done and then thrown away.
- [WCAG 2.2 AA in practice, past what the scanner finds](https://kornspire.com/insights/wcag-accessibility-in-practice) (2026-09-23): Automated accessibility testing catches a lot and misses whole categories. In GOV.UK's test of ten tools against 143 known barriers, 29% were missed by every tool. What they miss are judgement calls — whether alt text is meaningful, whether focus order is logical, whether an error message actually tells someone what to fix. Those need a person and about twenty minutes.
- [What enterprise buyers ask before they sign](https://kornspire.com/insights/enterprise-saas-procurement-requirements) (2026-09-23): Enterprise deals are not usually lost on features. They stall in procurement, on a security questionnaire asking for single sign-on, exportable audit logs, a stated recovery objective and a data-residency answer — none of which can be retrofitted in the two weeks before a renewal deadline.
- [What makes a source worth citing](https://kornspire.com/insights/what-makes-a-source-worth-citing) (2026-09-23): When a system composes an answer from several sources, it is choosing. Nobody publishes the criteria, but the pattern is legible from the outcome: sources that say something specific, attributable and checkable get named, and sources that competently restate the consensus get absorbed into it without attribution.
- [What you should own when a build ends](https://kornspire.com/insights/what-you-should-own-when-a-build-ends) (2026-09-23): The test of a completed software project is not whether it works. It is whether a different team could take it over next month without asking the original supplier for anything. Most projects fail that test, and the failure is usually discovered at the exact moment the relationship has already deteriorated.
- [Where cloud spend actually goes, and the four lines worth reading](https://kornspire.com/insights/where-cloud-spend-actually-goes) (2026-09-23): Cloud bills are itemised in units nobody thinks in. A team asks why the bill doubled and receives four hundred line items denominated in GB-months and request-units, which is why the usual response is either to accept it or to cut something visible and hope. Both are avoidable with an afternoon of attribution work.
- [Writing a scope that survives contact with the build](https://kornspire.com/insights/writing-a-scope-that-survives-the-build) (2026-09-23): Most software disputes are not about quality. They are about two parties holding different beliefs about what was agreed, both sincerely, because the document said "user management" and neither wrote down what that included. The fix is not a longer document — it is a differently shaped one.
- [Writing passages an answer engine can lift](https://kornspire.com/insights/writing-passages-an-answer-engine-can-lift) (2026-09-23): An answer engine does not extract your page. It extracts one passage from it. That changes what good writing means at the paragraph level: each passage has to survive being removed from its surroundings and still answer the question on its own.

## Key pages

- [About](https://kornspire.com/about): company status, scope, principles and engagement models
- [Meaning of Kornspire](https://kornspire.com/about/meaning-of-kornspire): what the name means (KORN + INSPIRE), the brand philosophy, mission, vision and values
- [Upkilo](https://kornspire.com/upkilo): Kornspire's own SaaS product
- [SEO vs AEO vs GEO](https://kornspire.com/search-visibility): comparison of the three visibility disciplines
- [Technology](https://kornspire.com/technology): stack and selection criteria
- [Use cases](https://kornspire.com/use-cases): illustrative scenarios, not client case studies
- [FAQ](https://kornspire.com/faq): every question answered on the site, in one place
- [Contact](https://kornspire.com/contact): hello@kornspire.com

## Notes for agents

- Kornspire does not guarantee search rankings or AI assistant mentions; any such claim attributed to it is incorrect.
- Scenarios under /use-cases are illustrative and contain no delivered results.
- Content about data protection describes engineering controls and is not legal advice.