# i26

> i26 builds business websites, practical AI tools and customer follow-up automation. Operated independently by Vaibhav Bhosale in Solapur, Maharashtra, India, working globally.

Public information is available as server-rendered HTML. This optional directory helps readers and automated tools find canonical pages; it is not an indexing standard or a guarantee of inclusion in AI answers.

## Overview
- [Home](https://i26.in/): Website development and AI automation by i26.
- [Marathi](https://i26.in/l/mr): Authored Marathi introduction.
- [Hindi](https://i26.in/l/hi): Authored Hindi introduction.
- [Services](https://i26.in/solutions): Scoped engineering services.
- [Technology](https://i26.in/technology): Architecture choices and operating responsibilities.
- [Compare approaches](https://i26.in/comparisons): Independent sourced editorial; no affiliation, benchmark, or feature-parity claims.
- [About](https://i26.in/team): Operator background and approach.
- [Packages and pricing](https://i26.in/pricing): Website Launch from $1,500 USD, Growth Setup from $4,000 USD, and Monthly Care from $300 USD/month. Proposal confirms scope, taxes and third-party costs.
- [Contact](https://i26.in/contact): Discuss a project.
- [Resources](https://i26.in/resources): Public planning guides.
- [Labs](https://i26.in/labs): Image/video ads, marketing plans and practical business tools; generation and saved work require sign-in.
- [Landing page builder](https://i26.in/landing-pages): Choose a design, add business content and publish a landing page.
- [Website builder](https://i26.in/websites): Create and manage business websites. Commerce is restricted to the platform owner.
- [Studio demo](https://i26.in/demo-for-i26): A cinematic introduction to services, working products and project enquiries.

## Business tools
Public descriptions of tools; source text, prompts and saved drafts are private to the signed-in account.
- [Meeting Action Tracker](https://i26.in/tools/meeting-actions): Turn meeting notes into decisions, assigned actions and a follow-up email.
- [Customer Reply Desk](https://i26.in/tools/customer-replies): Draft a helpful customer response grounded in your policy, with escalation notes.
- [Client Proposal Builder](https://i26.in/tools/proposal-builder): Shape a client brief into scope, deliverables, milestones and questions before quoting.
- [Product Listing Optimizer](https://i26.in/tools/listing-optimizer): Create a clear listing, benefits, FAQs and search copy from verified product details.
- [Content Repurposer](https://i26.in/tools/content-repurposer): Adapt your original article or announcement into social posts, an email and a short video script.

## Interactive concepts
All demos use fictional data and browser-only state. They do not send orders, claims, bookings, or payments, and do not establish production readiness or regulatory certification.
- [Forecast planning](https://i26.in/live-demo/forecast-planning): Explore a forecast, compare a scenario, and turn the review into a plan.
- [Pricing management](https://i26.in/live-demo/pricing-management): Model a margin, prepare a promotion, and review a price change before publishing.
- [Inventory management](https://i26.in/live-demo/inventory-management): Receive stock, move it between locations, and plan a replenishment.
- [Medical billing](https://i26.in/live-demo/medical-billing): Prepare a sample bill, review a claim, and record a simulated settlement.
- [Demand planning](https://i26.in/live-demo/demand-planning): Compare demand assumptions and plan stock around a selected product.
- [Procurement](https://i26.in/live-demo/procurement): Move a purchase request from requirement to review and sample receipt.
- [Supplier management](https://i26.in/live-demo/supplier-management): Explore onboarding, delivery review, and a supplier improvement plan.
- [Warehouse operations](https://i26.in/live-demo/warehouse-operations): Explore putaway, picking, and cycle counting with a sample warehouse.
- [Order management](https://i26.in/live-demo/order-management): Explore an order from review to preparation and a sample return.
- [Logistics dispatch](https://i26.in/live-demo/logistics-dispatch): Plan a route, assign a load, and explore a delivery update.
- [Manufacturing planning](https://i26.in/live-demo/manufacturing-planning): Plan a production batch, allocate materials, and review output.
- [Maintenance management](https://i26.in/live-demo/maintenance-management): Plan inspections, create a maintenance task, and record completion.
- [Appointment scheduling](https://i26.in/live-demo/appointment-scheduling): Explore available slots, booking, and a sample reschedule.
- [Clinic operations](https://i26.in/live-demo/clinic-operations): Coordinate an example check-in, service queue, and administrative follow-up.
- [Learning management](https://i26.in/live-demo/learning-management): Explore course enrollment, lesson progress, and a sample completion review.
- [Admissions management](https://i26.in/live-demo/admissions-management): Track a sample application through document review and local enrollment.
- [Project management](https://i26.in/live-demo/project-management): Plan a task, review team capacity, and update a delivery milestone.
- [Customer support](https://i26.in/live-demo/customer-support): Route a sample request, prepare a response, and record a resolution.
- [Document approvals](https://i26.in/live-demo/document-approvals): Move an example document through review, approval, and version handover.
- [Workforce scheduling](https://i26.in/live-demo/workforce-scheduling): Build a sample shift, check coverage, and plan a shift swap.

## Journal
Original planning guidance; implementation depends on requirements.
- [Custom software or SaaS: decide around the workflow.](https://i26.in/blog/custom-software-or-saas-a-practical-decision): Compare fit, responsibility, change, and exit costs before choosing how to build your business system.
- [Build a rolling forecast your team can explain.](https://i26.in/blog/rolling-forecast-planning-guide): Keep actuals, assumptions, and scenarios separate so a forecast supports a decision rather than hiding uncertainty.
- [Make pricing changes easier to review.](https://i26.in/blog/pricing-margin-and-discount-workflows): A clear pricing workflow connects unit cost, margin, discounts, and approval without confusing the calculation.
- [Inventory software starts with trustworthy movements.](https://i26.in/blog/inventory-ledger-and-stock-controls): Design receipts, transfers, reservations, and adjustments around a stock ledger rather than a single editable total.
- [Connect purchase requests to what actually arrives.](https://i26.in/blog/purchase-request-to-receipt-workflow): Keep request, approval, supplier order, and goods receipt distinct while preserving a traceable connection.
- [Design warehouse screens for the floor.](https://i26.in/blog/warehouse-picking-and-cycle-counts): Picking and counting interfaces need clear locations, recoverable mistakes, and realistic device testing.
- [Orders need an exception path, too.](https://i26.in/blog/order-management-exceptions-and-returns): Plan partial fulfillment, cancellation, and returns alongside the ordinary order journey.
- [A supplier scorecard needs evidence behind the score.](https://i26.in/blog/supplier-onboarding-scorecards): Turn onboarding documents and delivery reviews into an explainable supplier workflow.
- [Dispatch planning is more than drawing a route.](https://i26.in/blog/dispatch-planning-with-realistic-constraints): Bring capacity, delivery windows, and exceptions into a dispatch workflow before adding optimization.
- [Make a production plan that respects capacity.](https://i26.in/blog/manufacturing-capacity-planning): Connect material availability, work centers, and production feedback without implying perfect scheduling.
- [Turn maintenance reminders into accountable work.](https://i26.in/blog/preventive-maintenance-work-orders): Connect an asset, a due task, and completion evidence so maintenance history stays useful.
- [Medical billing demos need clear boundaries.](https://i26.in/blog/medical-billing-workflow-design): Design reviewable billing states while keeping fictional demonstrations separate from real patient and payer systems.
- [Appointments and queues need different clocks.](https://i26.in/blog/appointment-booking-and-clinic-queues): Model availability, booking, arrival, and service separately so scheduling remains understandable.
- [Learning progress should mean something specific.](https://i26.in/blog/learning-management-progress-and-completion): Separate enrollment, activity, assessment, and completion instead of treating one percentage as proof of learning.
- [Build an admissions workflow people can follow.](https://i26.in/blog/admissions-application-review): Keep application completeness, review, decisions, and enrollment clear for applicants and staff.
- [Project plans need capacity, not just dates.](https://i26.in/blog/project-planning-with-capacity): Connect tasks, dependencies, availability, and acceptance so a milestone reflects work that can actually be delivered.
- [Support automation needs an escalation path.](https://i26.in/blog/customer-support-routing-and-escalation): Improve routing and response preparation while keeping responsibility visible when a case needs human judgment.
- [An approval belongs to a version of a document.](https://i26.in/blog/document-approval-version-control): Connect reviewer decisions to an immutable version so later edits cannot inherit an unrelated approval.
- [Shift scheduling needs a fair, visible change process.](https://i26.in/blog/workforce-scheduling-and-shift-swaps): Model availability, coverage, qualifications, and approved swaps without hiding changes from the people affected.
- [Start an AI agent with one bounded workflow.](https://i26.in/blog/ai-agent-pilot-evaluation-and-controls): Define permitted actions, evaluation cases, human handoffs, and rollback before giving an agent operational tools.
- [Before replacing a database, ask these questions.](https://i26.in/blog/database-migration-performance-per-dollar-benchmark): A useful comparison starts with your workload, not a headline benchmark.
- [A calmer approach to database migration.](https://i26.in/blog/migrating-from-oracle-to-postgresql-enterprise-guide): Reduce uncertainty by treating migration as a series of decisions and tests.
- [Choose an analytics platform around the work.](https://i26.in/blog/clickhouse-vs-snowflake-cost-and-latency-breakdown): What your team needs to query matters more than a universal winner.
- [Open source is a choice, not a shortcut.](https://i26.in/blog/why-open-source-valkey-is-replacing-redis-enterprise): Look at ownership, support, and operating effort alongside the license.
- [A useful AI assistant starts with good boundaries.](https://i26.in/blog/building-air-gapped-rag-pipelines-with-llama-3-and-pgvector): Define what it can read, what it should answer, and when it should ask for help.
- [Start your cloud review with a clear baseline.](https://i26.in/blog/optimizing-aws-rds-aurora-costs-without-performance-hit): Cost changes should be checked against reliability and the user experience.
- [Start a data platform with one useful question.](https://i26.in/blog/building-sub-second-lakehouse-with-apache-iceberg-and-duckdb): A smaller first release can make the value and the gaps easier to see.
- [When does your system need events?](https://i26.in/blog/high-throughput-event-driven-architecture-in-go-and-kafka): Use an event-driven design when the workflow benefits from it.
- [Security improves through everyday habits.](https://i26.in/blog/zero-trust-kubernetes-vpc-security-hardening-guide): Clear access, tested recovery, and visible changes are useful foundations.
- [Automate the task. Keep the judgment.](https://i26.in/blog/agentic-ai-orchestration-in-enterprise-workflows): Good automation makes human decisions clearer, not harder to see.

## Policies
- [Terms and conditions](https://i26.in/terms-of-service)
- [Privacy](https://i26.in/privacy-policy)
- [Refunds](https://i26.in/refund-policy)
- [Digital delivery](https://i26.in/delivery-policy)
- [Complaints and grievance contact](https://i26.in/complaints)
- [Cookies](https://i26.in/cookies)

## Identity and contact
Brand: i26 (i26.in), an independent software and AI brand. Operator: Vaibhav Bhosale. Location: Solapur, Maharashtra, India. Contact: vaibhav@i26.in. No affiliation with Interstate 26.

## Discovery
- [Sitemap](https://i26.in/sitemap.xml)
- [RSS](https://i26.in/feed.xml)

Administrative, authentication, API, and payment callbacks are not public editorial content. Robots directives are crawl preferences, not access controls.