About AutoKaam

AutoKaam is an independent news, tutorials, and tool-directory site covering artificial-intelligence products from the angle of small and mid-sized business buyers. We publish at autokaam.com. The newsroom is operator-led, opinionated, and built around a simple proposition: most AI coverage in 2026 is written for hyperscalers, VCs, and prompt-engineers. Almost none of it is written for the procurement lead at a 60-person logistics firm trying to figure out whether to roll Claude or ChatGPT to her sales team next quarter. We try to be that second publication.

Who runs this

AutoKaam is owned and operated by Aditya Sharma, an independent builder and writer based in Delhi NCR, India. Aditya runs the editorial calendar, commissions and edits every piece, ships the engineering, and signs the cheques. There are no outside investors, no advertorial partners, and no paid product placements masquerading as editorial. AutoKaam is part of a small portfolio of self-funded internet products built solo from India.

Editorial decisions are independent of any current or former employer of the owner and are not coordinated with any AI vendor, distributor, or reseller. When Aditya has a personal stake in a product or competitor relevant to a piece, that stake is disclosed inline.

What we cover

The site is divided into four surfaces, each with a distinct editorial job:

• News— daily reporting on AI launches, pricing changes, model releases, regulatory actions, and procurement- relevant moves from US, EU, India, and China-based vendors. Stories are framed from the buyer’s seat, not the developer’s.
• Tutorials— applied walk-throughs that show, end-to-end, how to deploy a tool to solve a specific recurring SMB problem (lead-routing, contract review, support triage). Real screenshots, real numbers, real failure modes.
• Tool directory— an opinionated catalogue of AI products organised by what the buyer is trying to do, with the contract clauses procurement actually reads (data-residency, indemnity, SOC2, on-premise availability, GST treatment).
• AI directory— a comparative reference table for the most-asked tool categories, refreshed when material specs change.
• Compare— head-to-head deep dives between products that buyers genuinely shortlist together, updated when one side ships a meaningful change.

Editorial angle

Our internal frame is “operator-grade.” That means three commitments:

• Verdict over coverage. Every story ends with a clear take. We do not publish two-sides-to-every-story stenography of vendor press releases. If a launch is a strategic move, we say what against. If a price cut is bait, we say so.
• Numbers as subjects.Headlines and decks use the actual amount, seat count, latency, or context window when the story turns on it. Vague adjectives (“massive,” “industry-leading,” “game-changing”) are banned in our internal style guide.
• Named stake. Every story names who loses and who wins from the development being covered. If we cannot name a stake, the story is not ready to publish.

How articles get made (and our AI-assistance disclosure)

AutoKaam is transparent about its workflow because readers deserve to know how the words they are reading came to be on the page.

A story typically starts with a primary source: a vendor announcement, a regulatory filing, an SEC document, a benchmark release, a maintainer’s blog post, a published dataset. From that source, our drafting workflow uses large language models — primarily Anthropic Claude and Cerebras-hosted open models — to accelerate research synthesis, structure articles to the editorial frame above, and enforce style-guide rules. Every published article is then reviewed by a human editor (the owner, in most cases) for factual accuracy, attribution, and angle before it goes live. Quotes, dollar figures, model names, dates, and version numbers are checked against the primary source.

We do not publish wholesale model output as editorial. We do not invent quotes. We do not fabricate sources. When a model gets something wrong in draft, we correct it in edit. When an error makes it to publication, we correct it with a dated note on the article (see “Corrections” below).

Author personas on the site (for example, contributors who file from a specific regional or product-vertical angle) reflect editorial roles and reporting beats. The site is run by a single operator and a writing assist stack, not a multi-person newsroom; we believe naming the beat is more useful to readers than reusing the same byline on every story.

Sources, attribution, and originality

Every news article on AutoKaam links out to its primary source on first reference. When we paraphrase a competitor’s reporting we attribute it inline and link back. When we use a quote that originated in another publication we say so. When a story rests on a single rumour-tier source we label it as such.

Original written content on the site is copyright AutoKaam. You are welcome to quote short excerpts (a paragraph or two) with a clear attribution and a link back to the source URL. Wholesale republishing or full translation requires written permission; email [email protected].

Imagery

Hero and inline imagery is sourced from Unsplash, Pexels, Wikimedia Commons, publisher pages, and the duotone CSS treatment we apply over them for visual consistency. We do not use AI-generated illustrations to depict real people, real products in fictional states, or events that did not happen. We do not host reader-uploaded images.

How we make money

AutoKaam is reader-supported through display advertising served by Google AdSense and other ad networks. We may add additional monetisation surfaces over time (sponsored newsletter sections, premium tools, paid research downloads); when we do, they will be clearly labelled as such, and editorial coverage will remain independent of any advertiser relationship.

We do not accept paid placements presented as editorial. We do not run sponsored content inside the news flow. Affiliate links, where used, are disclosed at the top of the article and do not influence the verdict.

Corrections

When a published article contains a factual error — a wrong dollar amount, a mis-stated launch date, an attribution to the wrong company, a misquoted source — we correct it on the original URL and add a dated correction note at the foot of the article describing what changed. We do not silently rewrite history. If you spot something to correct, write to [email protected] with the URL and the mistake.

Tips, pitches, and right of reply

We read every editorial tip. The fastest way to reach the desk is [email protected]. If you are a vendor who feels we got something wrong about your product, mail the same address and we will look at it on the same news cycle wherever practical. We honour right-of-reply requests for live disputes when they are sent before press.

Unsolicited PR mass-blasts do not get coverage and are not acknowledged.

Where the site is hosted

AutoKaam is built as a Next.js static export and deployed on Cloudflare Pages, with Cloudflare as the CDN and DNS provider. Deploys are automated from a private codebase. The site has no logged-in user surface and no comment system. Reader logs are described in our Privacy Policy.

Contact

Editorial, corrections, takedowns, and partnership enquiries: [email protected]. See also our contact page, Privacy Policy, and Terms of Use.

AutoKaam is operated from Delhi NCR, India.