Insights
Articles for founders and teams facing a technology decision, on websites, apps, AI and automation, data, security, hosting, search and brand. Each one answers a single question, and the people who do the work write them.
52 articles across 10 topics
Three shades of the same blue and a stretched logo make a business look unsure of itself. The sections a small business guideline needs, and what to leave out so people use it.
Questions it answers
A site can look fine to you and still be hard for Google to reach or read. What a technical SEO audit checks, and what a useful report should hand you at the end.
Your first automation decides whether the team trusts the next one. Start with frequent, rule-based, low-risk tasks, and use a simple score to choose between them.
Pick your host by who will look after the server, not by the monthly fee. Shared, managed, VPS, cloud or platform: what each one asks of you in effort and control.
Some tasks need an AI agent and many are better served by plain automation. A simple test: how often it happens, what it costs your team, and whether the result can be checked.
Before you build on WhatsApp, know the rules: who you may message, what you can send outside the reply window, and where businesses usually get stuck.
A parent on a phone wants quick answers: can my child get in, what does it cost, is it safe, how do I reach you. The pages and details every school website needs.
Forms stop sending, certificates expire, and every small change becomes a new project. What a website care plan should cover, and the questions to ask before you sign one.
Billing, invoices, tax, support and security are invisible when they work and very visible when they don't. What a SaaS product needs in place before it takes its first payment.
Listening, taking stock, fixing the biggest risks, then a roadmap you can act on. What a part-time technology lead does when they start, and what you should have at the end.
A customer or regulator wants a VAPT report, or you are about to launch logins and payments. What the test is, when you need one, and what to do with the report.
Before investors or a buyer commit, someone will look hard at your technology. What they check, what raises concern, and the cheap fixes to make before the review starts.
If your invoices land in spam, or someone sends email that looks like yours, these three DNS records are usually why. What each does and how to set them up safely.
Both work well in India. The right one depends on your catalogue, your team and who looks after the store once it is live. A fair comparison on payments, GST, shipping and ownership.
Most schema types promise rich results a service business will never get. The few that do real work, a JSON-LD example, and the mistakes that waste the effort.
Your customers pay in dollars, dirhams or pounds, and the money has to land in an Indian bank account. How to choose a gateway you can get approved on, and what to check first.
Before you pay for two apps, check whether one would do, or whether a good mobile website would. How to choose between native, React Native, Flutter and the web for a first app.
Your visitors should barely notice the move, apart from faster pages. What changes for the people who edit the site, and how to carry your URLs and rankings across.
When someone nearby searches for what you do, a few businesses show up on the map. How a Pune business gets into that list, from Google Business Profile to honest reviews.
Someone told you to add an llms.txt file. It is cheap and harmless, but no major AI search product has confirmed it reads one. What it is, and what to do before it.
A customer has asked whether you are ISO 27001 certified. What the standard asks of a small company, what the work looks like, and how to tell whether certification is worth it yet.
If your cloud bill grows faster than your business, money is leaking somewhere. The seven places it usually goes, and how to check each one from your billing console.
Staff pasting customer data into unapproved tools is a bigger risk than the model itself. What to ask AI vendors, and the controls to put in place before you connect anything.
A vague brief gets quotes you cannot compare. A plain template for a website, app or software brief, with the questions that matter most and the mistakes that ruin it.
The developer has gone quiet and the app is half built. How to find out what you own, what state the code is in, and whether to fix it, rebuild it or walk away, without paying twice.
Nobody can promise you a place in an AI answer, but you can make it much more likely. The steps that matter, in the order to do them, from crawler access to clear answers.
A slow page loses visitors before they read a word. What Google's three Core Web Vitals measure, the targets it publishes, and the fixes that move the numbers on most business sites.
Sooner or later someone will ask to see, correct or delete the data you hold on them. A workable way to receive, verify and answer those requests, even with a small team.
Two quotes for the same project can be far apart, and both can look reasonable. What to send an independent reviewer, what they check, and the red flags to catch before you sign.
Someone on your team is retyping orders and leads from one system into another. How to connect your website or app to Tally, Zoho or your CRM, and plan for the day a transfer fails.
Most dashboards stop being opened the first time someone doubts a number. Start from the decisions, pick a few figures, clean the data underneath, and build one people trust.
Every feature you add before launch is a guess you pay for. How to find the smallest version that lets one real user finish the one job your product exists for.
Compliments are not demand. How to find the people who have the problem, test what they will actually do, and decide to build, change or stop before you spend on development.
Page views tell you who visited. Events tell you who got in touch. The short list of GA4 events that shows whether your website brings in enquiries, and how to set them up.
The DPDP Act reaches almost every business that collects customer or staff details. The first steps to take, in the order that saves you redoing work later.
If Google Analytics runs on your site and your visitors are in India or the Gulf, the law may expect consent. What each market asks, and how to keep useful data when people say no.
Buy when your process is the same as everyone else's. Build when the process is what sets you apart. The questions that settle it, and the costs that only show up later.
The DPDP Act never mentions cookies, yet its consent rules reach your analytics and ad trackers. What an Indian website should change, and how to test that consent really works.
If a cyber incident hits your business, CERT-In expects a report within six hours of noticing it. Who has to report, what counts, and what to set up before that day comes.
Customers ask the same questions on WhatsApp at all hours. An AI assistant can answer the routine ones from your own information and pass the rest to a person.
A backup you have never restored is only a hope. The 3-2-1 rule, how much data and downtime you can afford to lose, and a short recovery plan a small team can keep up.
Three acronyms, one worry: will people find you on Google and in AI answers? What each one means, where they overlap, and why one plan usually covers all three.
People now ask ChatGPT a question and act on the answer without clicking a result. Why ranking on Google is still needed but no longer enough, and what gets a business cited.
Rented software only ever did part of the job, and someone else's roadmap decided the rest. Why we built three products of our own, and what that changes for your work.
The proposal goes out, the reply says "let us think about it", and then nothing. How a follow-up sequence planned in advance brings those conversations back.
Everyone says speed matters, and most sites still ship heavy and slow. Why a hard number checked on every change is what keeps a site fast, and the one we hold ourselves to.
Turning down paying work felt reckless at first. The warning signs of a bad fit we now watch for, and why saying no more often made the work better for everyone.
We rebuilt how we deliver around AI in early 2023. What it changed, what we still keep with people, and what to ask any agency about how it uses AI on your work.
The best websites feel as if nothing on them could move. That comes from removing, not adding. Why restraint is hard, and the questions we ask before designing a page.
Growing businesses in India are often sold a rushed site, an overpriced proposal or a template. What they need instead, from what we have learned across 15+ industries.
Telling people they need less, pointing them elsewhere when we are not the right fit, staying after launch. Why putting the work first turns out to be good business.
Most digital work is built to ship, not to last, and the business pays for the rebuild. What quality means in practice, and the six things we will not trade away on any budget.
How we write
Every article starts from something a founder or a team asked us, and answers it in the first two lines.
Where a rule or a number comes from Google, CERT-In or the DPDP Act, we name the source and link to it.
The team that designs, builds and looks after the work writes these too. No ghostwriters.
