DEV Community: ashiq

I Built a Free UPSC Photo Resizer After Seeing How Frustrating Government Form Uploads Can Be

ashiq — Thu, 04 Jun 2026 09:09:26 +0000

The Problem

If you've ever filled out a government application online, you've probably seen errors like:

File size too large
Invalid image dimensions
Signature upload failed
Photo format not supported

The frustrating part is that your photo looks perfectly fine, but the portal still rejects it.

While building image tools, I noticed that many users were specifically looking for ways to resize photos for exams and government applications.

That's when I decided to create a simple solution.

What Users Actually Need

Most people don't want a complex photo editor.

They simply want to:

Upload a photo
Choose the required size
Download the result
Submit their application

That's it.

Building the Tool

I built a browser-based image resizing tool that allows users to:

Resize images
Compress photos
Reduce file size
Convert formats

without installing software.

One interesting discovery was how many searches were related to:

UPSC photo resize
Aadhaar photo resize
PAN signature resize
Government form image compression
Lessons Learned

Small Problems Matter

Many developers chase huge startup ideas.

Sometimes solving a simple problem can help thousands of people.

SEO Reveals Real User Needs

Looking at search queries often reveals pain points you never considered.

Distribution Is Harder Than Development

Building the tool took less time than getting users to discover it.

That's why I've been learning SEO, content marketing, and programmatic landing pages.

Current Progress

The project is still growing, but it's already receiving impressions from Google Search for image resizing and compression queries.

Every day I learn a little more about building products, SEO, and solving real user problems.

Try It

If you'd like to resize or compress images online, you can try:

optikit.co.in

Feedback is always welcome.

A Client Asked for a Proforma Invoice. I Had No Idea What That Was.

ashiq — Tue, 02 Jun 2026 12:52:00 +0000

A few years ago, if someone had asked me what a proforma invoice was, I probably would've guessed.

And I would've guessed wrong.

The term sounds complicated.

The concept isn't.

What Happened

A client requested a proforma invoice before approving a project.

I assumed they wanted a normal invoice.

They didn't.

They wanted an estimate.

Something that outlined pricing before committing to the work.

That's exactly what a proforma invoice is.

Why Businesses Use Them

A proforma invoice helps:

Confirm pricing
Set expectations
Obtain approvals
Prevent misunderstandings

It's especially common in international business and freelance projects.

The Simple Explanation

A proforma invoice is a proposal.

An invoice is a payment request.

That single distinction makes everything easier to understand.

Creating Proforma Invoices

After learning how often businesses use them, I added support for generating proforma invoices online.

https://docforge.website/tools/proforma-invoice-generator

Final Thought

Sometimes the business terms that sound the most intimidating are actually the simplest.

A proforma invoice isn't complicated.

Most people just haven't been taught what it does.

I Discovered Why So Many Freelancers Hate NDA Templates

ashiq — Tue, 02 Jun 2026 12:51:10 +0000

Recently I needed a simple NDA.

I expected the process to take five minutes.

Instead, I spent nearly an hour searching through templates.

The surprising part?

The templates weren't terrible.

They were just unnecessarily complicated.

The Common Problems

Most NDA templates I found had one or more of these issues:

Legal jargon everywhere
Outdated formatting
Forced downloads
Required signups
Poor mobile experience

For someone who simply wants to protect confidential information, the process felt far harder than it should.

Why Simplicity Matters

Most freelancers don't need a custom legal document drafted from scratch.

They need a straightforward confidentiality agreement that covers the essentials.

The easier the process becomes, the more likely people are to actually use NDAs when appropriate.

Building a Better Alternative

That frustration inspired me to build a free NDA generator.

The goal was simple:

Reduce complexity.

Generate documents quickly.

Make the experience accessible.

https://docforge.website/tools/nda-generator

Final Thought

Many software ideas start with a small annoyance.

This one started with an NDA template that should have taken five minutes but didn't.

I Thought an Invoice and a Receipt Were the Same Thing. I Was Wrong.

ashiq — Tue, 02 Jun 2026 12:50:07 +0000

For years, I casually used the words invoice and receipt as if they meant the same thing.

Most people do.

The problem is that they're completely different documents.

And confusing them can create accounting headaches.

The Moment I Realized the Difference

I was helping someone organize business documents when they asked:

"Can you send me the receipt?"

I sent the invoice.

They replied:

"No, I need proof that I've already paid."

That was the moment everything clicked.

Invoice vs Receipt

An invoice is sent before payment.

A receipt is sent after payment.

That's it.

One requests money.

One confirms money was received.

Why This Matters

Using the wrong document can create:

Client confusion
Accounting issues
Tax reporting mistakes
Poor record keeping

Many small businesses accidentally mix them up.

Creating Receipts Quickly

The easier it is to generate professional receipts, the easier it becomes to maintain proper records.

That's one reason I built a receipt generator.

https://docforge.website/tools/receipt-generator

Final Thought

The simplest business lessons are often the most expensive to learn.

Invoice = request for payment.

Receipt = proof of payment.

Remembering that distinction can save a lot of confusion.

I Sent an Invoice and Didn't Get Paid. The Problem Wasn't the Client.

ashiq — Tue, 02 Jun 2026 12:48:39 +0000

A few years ago, I thought getting paid was simple.

Finish the work.

Send the invoice.

Wait for the money.

But reality turned out to be very different.

One project after another, I noticed a pattern. Some clients paid immediately. Others delayed payments for weeks.

At first, I blamed the clients.

Then I started looking at the invoices themselves.

And that's when I realized the problem wasn't always on their side.

The Missing Details

One invoice didn't include payment terms.

Another didn't have a due date.

A third was missing an invoice number entirely.

Small mistakes created unnecessary questions.

Questions created delays.

Delays created late payments.

Why Professional Invoices Matter

A good invoice isn't just a document.

It's a communication tool.

A professional invoice should clearly show:

Business details
Client information
Invoice number
Due date
Payment terms
Itemized services
Total amount due

The easier it is for clients to understand your invoice, the faster they can process it.

Why I Built a Simpler Solution

After repeatedly dealing with invoice templates and spreadsheets, I wanted a faster way to generate professional invoices.

That's what led me to build a free invoice generator.

Instead of editing templates manually, users can generate invoices in minutes.

https://docforge.website/tools/invoice-generator/global

Final Thought

Sometimes getting paid faster isn't about finding better clients.

It's about sending better invoices.

Stop Paying for Invoice Software These Free Browser Tools Do Everything

ashiq — Mon, 01 Jun 2026 08:38:12 +0000

I've been freelancing for a couple of years, and for the longest time I was either paying for invoicing software I barely used or downloading clunky templates that broke the moment I opened them on a different machine.

Then I realized: everything I need to bill a client can be done in a browser. No signup, no subscription, no app to install.

Here's the stack I actually use now — and why each one earns its place.

1. GST Invoice Generator (for Indian freelancers)

If you're billing Indian clients, you know the pain of getting GST formatting right. Wrong CGST/SGST split, missing HSN codes, wrong invoice series — and your client's accountant sends it back.

I use the GST Invoice Generator on DocForge for all domestic Indian billing. It handles:

CGST + SGST split for intra-state
IGST for inter-state
HSN/SAC code fields
Sequential invoice numbering

There's also a product-specific GST invoice variant if you're selling physical goods rather than services. Took me 2 minutes to generate a GST-compliant invoice the first time I used it.

If you're a freelancer filing ITR or working with clients who need proper GST invoices for their input tax credit, this one matters.

2. Global Invoice Generator

For international clients, GST doesn't apply — but you still need a clean, professional invoice.

The Global Invoice Generator covers country-specific formats. I've used it for clients in:

Canada — includes HST/PST fields
UAE — VAT-ready
Australia — ABN field included

The professions variants are also solid. I used the Developer invoice template for a recent contract — it pre-formats the line items in a way that makes sense for hourly dev work.

3. Receipt Generator

Invoices are for billing. Receipts are for confirming payment was received.

The Receipt Generator is underrated — most tools conflate the two. This one is specifically for generating payment receipts, which is what you send after the invoice is settled.

Super useful for:

Freelancers who need to provide proof of payment receipt
Small business owners who deal with cash or offline transactions
Anyone whose client asks for a receipt to log expenses

4. VAT Calculator

Quick one. If you're dealing with European clients and need to figure out VAT-inclusive vs VAT-exclusive pricing before putting it on an invoice, the VAT Calculator is right there.

It supports UK, Germany, and other EU country rates. No conversion needed, just plug in the number and get both the VAT amount and the gross total.

5. Proforma Invoice Generator

If a client needs a quote before the work starts — or if you're dealing with customs/import situations — a proforma invoice is what they need, not a standard invoice.

The Proforma Invoice Generator handles this exactly. Same fields as a regular invoice but clearly marked as proforma so there's no confusion about whether payment is due.

6. Quotation Generator

Before the invoice, there's the quote. The Quotation Generator covers this — and it has profession-specific variants that are actually useful:

Professional quotes with the right line item structure for each type of work.

7. Salary Slip Generator

If you run a small team or need to generate payslips for employees (or yourself, if you're a one-person company paying yourself a salary), the Salary Slip Generator saves you from building a payslip template from scratch every month.

8. Credit Note Generator

Mistakes happen — wrong amount on an invoice, cancelled order, return. A credit note is the formal document that cancels or adjusts a previous invoice.

The Credit Note Generator is one of those tools you won't need often, but when you do, you really need it formatted correctly.

The Bigger Picture

All of these tools live at docforge.website — a browser-based document generation platform. Everything runs client-side, nothing is stored, and you can download your PDF immediately.

No account. No email capture. No watermark on the free version.

For Indian freelancers especially, I wrote a deeper guide: GST for Indian Freelancers — What You Actually Need to Know. It covers registration thresholds, invoice requirements, and how to handle international payments when you're GST-registered.

If you've been using Word templates or paying for invoicing SaaS for simple freelance billing, these tools will cover 90% of your use case for free. Browser-based, instant, and the output actually looks professional.

What invoicing setup are you currently using? Drop it in the comments.

I Found an Unexpected SEO Opportunity While Building Utility Tools

ashiq — Mon, 01 Jun 2026 08:07:33 +0000

When people talk about SEO opportunities, they usually mention finance, health, AI, or productivity.

Very few people talk about government application uploads.

But while building utility tools, I discovered something interesting.

Thousands of people struggle with a problem that sounds incredibly simple:

Uploading a photo.

The Problem

Imagine spending hours filling out an important application.

You enter your details.

Upload your documents.

Review everything.

Then the website shows:

"Photo size exceeds the allowed limit."

Or:

"Invalid image format."

Or:

"Image upload failed."

Suddenly a 2-minute task becomes a frustrating cycle of trial and error.

The UPSC Example

One search query kept appearing repeatedly:

UPSC photo compressor
Compress photo for UPSC
UPSC image size
UPSC photo upload error

At first, I thought this was a niche issue.

Then I realized thousands of applicants face the same problem every year.

Most people already have a valid photo.

The issue is usually:

File size too large
Wrong dimensions
Unsupported format

Why Existing Solutions Feel Frustrating

Many users end up visiting random image compression websites.

The experience often looks like this:

Upload image
Compress image
Download image
Upload to application portal
Get another error
Repeat

Some tools add watermarks.

Others destroy image quality.

Many are overloaded with ads.

Building a Simpler Solution

Instead of creating another generic image compressor, I built a dedicated UPSC Photo Compressor.

👉 https://optikit.co.in/compress-image-for-upsc

The goal was straightforward:

Upload image
Compress image
Download image

No sign-up.

No software installation.

No unnecessary steps.

The SEO Lesson

This project taught me something important.

Developers often chase exciting ideas.

Users search for practical solutions.

Nobody searches for:

"Next-generation AI-powered image optimization platform"

People search for:

"UPSC photo compressor"

The search intent is clear.

The problem is real.

The demand already exists.

Small Problems Can Be Big Opportunities

One thing I've learned while building SaaS products is that useful doesn't have to mean revolutionary.

Sometimes the best opportunities come from solving a very specific problem for a very specific group of people.

A simple utility that saves someone 15 minutes can be more valuable than a complicated product nobody understands.

What I'm Learning

Building tools is only part of the journey.

Distribution matters.

SEO matters.

Understanding user intent matters.

And most importantly:

Real problems are easier to market than clever ideas.

That's a lesson I wish I had learned earlier.

Have you ever built a tiny tool that ended up solving a much bigger problem than you expected?

I Thought Building the Tool Was the Hard Part. I Was Wrong.

ashiq — Mon, 01 Jun 2026 08:02:45 +0000

When I started building my SaaS products, I believed the difficult part would be writing code.

I thought if I built something useful, users would eventually find it.

Reality was very different.

Building the product was only the beginning.

The real challenge started after deployment.

The Dream

Most developers imagine a simple path:

Build product → Launch → Get users

It sounds logical.

Unfortunately, the internet doesn't work that way.

Thousands of products launch every week.

Most receive little to no attention.

My First Lesson

Traffic is not automatic.

I remember publishing a tool and checking analytics every few hours.

Nothing happened.

No visitors.

No signups.

No feedback.

Just silence.

At first, I thought the product wasn't good enough.

Later I realized a different problem existed:

Nobody knew it existed.

What Changed

Instead of focusing only on building, I started focusing on distribution.

That meant:

Writing Medium articles
Publishing on Dev.to
Learning SEO
Submitting to directories
Answering questions online
Improving landing pages

The amount of time spent promoting eventually became larger than the time spent building.

The Surprising Part

The biggest opportunities came from solving boring problems.

Not AI.

Not blockchain.

Not the latest trend.

Simple problems.

Things people search for every day.

Questions like:

How do I resize an Aadhaar photo?
How do I compress an image for UPSC?
How do I reduce an image below 200KB?

These aren't exciting startup ideas.

But they are real problems.

What I'm Building

One of the projects I'm currently working on is OptiKit.

The goal is simple:

Help people solve common image and document preparation problems without installing software.

https://optikit.co.in

Nothing revolutionary.

Just useful.

What I Believe Now

Many developers spend years waiting for a perfect startup idea.

I think a better approach is:

Find a small problem.

Solve it well.

Talk about it consistently.

Improve it over time.

The internet rewards persistence far more than perfection.

I'm still early in the journey, but that's the lesson building SaaS products has taught me so far.

What surprised you most after launching your first product?

I Built an Aadhaar Card Resizer After Watching People Waste 30 Minutes on a 2-Minute Problem

ashiq — Mon, 01 Jun 2026 07:29:19 +0000

A few months ago, I noticed something interesting.

People weren't asking for complex software.

They weren't asking for AI.

They weren't asking for automation.

They were asking:

"How do I resize my Aadhaar card photo?"

At first, it sounded like a tiny problem.

Then I watched how people actually solved it.

The Reality

Someone needs to upload a photo for a form.

The portal has strict requirements.

The image is too large.

So they:

Search Google
Open random image compression websites
Upload the image
Download it
Try uploading again
Get another error
Repeat the process

What should take two minutes often takes twenty.

The Hidden Opportunity

As developers, we often think valuable products need complicated technology.

But many of the best opportunities come from simple frustrations that millions of people experience.

Aadhaar-related image requirements are one of those frustrations.

Every day, people search for things like:

Aadhaar card photo resize
Aadhaar image size
Aadhaar photo compressor
Resize Aadhaar card online

The demand already exists.

The problem already exists.

The only question is whether someone solves it well.

Building a Simple Solution

Instead of creating another generic image tool, I built a dedicated Aadhaar Card Resizer.

👉 https://optikit.co.in/aadhaar-card-resizer

The goal was simple:

Upload image
Resize image
Download image

No registration.

No watermarks.

No unnecessary features.

What Building This Taught Me

One lesson stood out.

Most users don't care about features.

They care about outcomes.

Nobody wakes up wanting to use an image resizer.

They want to submit their application successfully.

The tool is simply a bridge between the problem and the outcome.

SEO Lessons From a Tiny Utility Tool

Working on this project also taught me a few lessons about SEO.

Search Intent Beats Creativity

Developers love creative names.

Users search for practical solutions.

"Aadhaar Card Resizer" is boring.

But it's exactly what people type into Google.

Small Problems Can Have Massive Demand

A problem doesn't need to be exciting to generate traffic.

Sometimes the boring problems are the biggest opportunities.

Distribution Matters More Than Building

Building the tool took less time than promoting it.

Writing articles, answering questions, and improving SEO has become a much bigger part of the journey.

Final Thoughts

The internet is full of complicated products chasing complicated problems.

Sometimes the best products solve simple problems better than everyone else.

That's exactly what I'm trying to do with OptiKit.

If you're curious, you can try the Aadhaar Card Resizer here:

👉 https://optikit.co.in/aadhaar-card-resizer

Have you ever built a small utility that ended up being more useful than you expected?

I Didn't Expect a Government Photo Tool to Become One of My Most Visited Pages

ashiq — Mon, 01 Jun 2026 07:27:22 +0000

When I started building utility tools, I thought developers would be the primary users.

I was wrong.

One of the most common problems people face online has nothing to do with code.

It's image uploads.

Every week, people search for things like:

Aadhaar photo resize
UPSC photo compressor
PAN card signature size
Passport photo dimensions

And surprisingly, many existing tools make the process harder than it needs to be.

The Problem

A typical smartphone photo today can be several megabytes in size.

Many government portals only allow uploads under specific limits.

The result?

People end up:

Trying multiple websites
Downloading random software
Re-uploading files repeatedly
Receiving "File size too large" errors

Something that should take 30 seconds often turns into a frustrating experience.

What I Built

Instead of creating another generic image compressor, I started building tools around specific use cases.

For example:

Aadhaar Card Resizer
UPSC Photo Compressor
PAN Card Image Resizer
Passport Photo Size Tools

One example:

👉 https://optikit.co.in/compress-image-for-upsc

The goal was simple:

Upload → Compress → Download

No sign-up.
No watermarks.
No unnecessary steps.

What Surprised Me

The biggest lesson wasn't technical.

It was discovering how much search demand exists around small, boring problems.

As developers, we often think innovation means building complex systems.

Sometimes people just want to upload a photo and move on with their day.

SEO Lessons Learned

A few things I've learned while building utility tools:

Search Intent Beats Features

Users don't search for:

"AI-powered image optimization platform"

They search for:

"UPSC photo compressor"

Specific Pages Perform Better

A dedicated page for a single problem often performs better than a generic all-in-one tool.

Real Problems Generate Traffic

The best ideas usually come from recurring frustrations people already experience.

What's Next

I'm continuing to build and improve small utility tools while learning SEO along the way.

The project is still early, but it's already teaching me an important lesson:

You don't always need a revolutionary startup idea.

Sometimes solving a simple problem well is enough.

Have you built a small tool that ended up being more useful than you expected?

I'd love to hear about it.

The First 100 Clicks Are Harder Than the First 10,000

ashiq — Sat, 30 May 2026 08:31:48 +0000

Everyone dreams about 10,000 users. Nobody talks about the first 100 clicks.
The first 100 clicks are strange. They arrive slowly one today, three tomorrow, maybe none the next day. Yet every single one feels important because a real person somewhere found something you built.

The Reality of Starting From Zero
When I launched DocForge I imagined growth would be easier. Not easy, just easier. I thought if I built useful tools people would eventually find them.
What I underestimated was how much of the internet is invisible. You can build something genuinely useful and still have nobody discover it. Not because the product is bad, not because people don't need it simply because nobody knows it exists. That's where the real challenge begins.

The Day I Became Obsessed With Search Console
You publish a page, request indexing, then you wait. A few days later you open Search Console zero clicks. Check again tomorrow, still zero. Then one day something changes. An impression appears. A few days later another. Then a click.
To most people one click is meaningless. To a founder it's proof. Proof that Google noticed your page, proof that someone searched for something, proof that your work exists outside your laptop.

The Problem With Startup Advice
Most startup content focuses on big numbers 10,000 users, 100,000 visitors, millions in revenue. Those stories are inspiring but they skip the hardest part. The beginning. The phase where nobody is watching, where you publish content that gets no traffic, where every graph looks flat.
That's the stage where most projects quietly die. Not because they fail because the founder loses patience.

What Actually Started Moving the Needle
I tried a bit of everything directory submissions, content updates, internal linking, community participation, SEO improvements. Some things worked better than others but one lesson kept repeating itself.
Consistency mattered more than intensity. A single day of hard work rarely changed anything. Thirty days of small improvements started creating signals. Not massive signals, but enough to show progress. And progress is what keeps you going.

Why the First 100 Clicks Matter
The first 100 clicks teach you things analytics tools can't. You start noticing which pages attract impressions, which topics people actually care about, which headlines get ignored, which assumptions were completely wrong.
Before that point you're mostly guessing. After that point you're learning. That's a huge difference.

The Emotional Rollercoaster Nobody Mentions
One day impressions go up and you feel brilliant. Next day traffic drops and you wonder if you broke everything. A week later rankings improve then fall again. The funny thing is the work often stays the same only the numbers change. Learning not to overreact to every graph has been one of the most valuable things I've picked up.

Small Wins Compound
A new backlink. A page moving up a few positions. A handful of clicks. A comment from a user. None of these look impressive individually but together they create momentum. Most successful products weren't built through a single breakthrough they were built through hundreds of small improvements stacked on top of each other.

Still learning, still experimenting, still making mistakes. But I no longer underestimate small numbers because every large number starts as a small one. Every successful website starts with a single visitor. Every meaningful graph starts at zero.
One of the projects I'm growing through all of this is DocForge a platform for generating professional business documents like invoices, NDAs, agreements and templates. Building it has given me a front row seat to the realities of SEO, product development, and patience.

I Built a SaaS, Did SEO for 30 Days With Zero Budget, and Here's the Uncomfortable Truth

ashiq — Sat, 30 May 2026 08:23:48 +0000

The startup advice sounds clean. Build, do SEO, get traffic, get customers. What nobody tells you is the part in between those arrows. The silence. The doubt. The "is this even working?" at 2am.
Thirty days ago I made a decision no agency, no paid ads, no shortcuts. Just me, a laptop, and an obsession with a dashboard that showed mostly zeros.

Day 1 I felt unstoppable.
Published pages, wrote content, fixed metadata, added internal links, submitted everything to Google Search Console. Then I waited. Refreshed. Waited some more. Nothing.
Nobody warns you about the silence. SEO in the first week doesn't feel like progress, it feels like shouting into a room and wondering if the walls even exist. You're used to instant feedback loops push code see results, ship a feature users respond. SEO gives you nothing. Just a flat graph and your own thoughts.

Then something small happened.
A few impressions showed up. Then a click, just one. Most people would scroll past this but when you've been staring at zeros a single click feels like confirmation that the internet knows you exist. Google noticed my site. That was enough to keep going.

Week two I fell into the trap every founder falls into.
More pages, more content, more backlinks, more everything. Classic founder brain. But then I actually looked at Search Console properly and saw something that changed my whole approach two or three pages were doing almost all the work, the rest were invisible.
So I stopped creating new pages and started improving the ones already getting impressions. Better titles, clearer intent, stronger FAQs, deeper internal links. That's when the graph stopped being flat.

The most boring work was the most effective.
Improving existing content beat publishing new content. Fixing page intent beat adding keywords. Strengthening internal links beat chasing backlinks. Search engines don't care that your process felt creative, they care that the page answered the question better than anyone else.

The emotional rollercoaster is real.
Day 18 plus 40% impressions, "oh my god it's working." Day 19 traffic drops, "I broke something." Day 22 rankings climb again, no idea why. SEO punishes people who need constant validation and rewards people who stay consistent anyway. That tension taught me more about patience than anything else I've built.

The biggest surprise wasn't traffic or rankings.
It was that Google rewards focus. The more I narrowed around one specific topic cluster the faster everything connected. Pages started referencing each other naturally, content started making sense as a system. The website stopped feeling like random pages and started feeling like something someone built on purpose.

Still learning, still refreshing GSC at unhealthy hours. Strategy is simple now improve pages already getting impressions, build topical authority, write for humans first, stay consistent even when the graph lies to you. No hacks, no agency, no secrets. Just slow compounding execution.
One honest note I wrote this while I was supposed to be doing SEO work. Make of that what you will.
If you're curious what I'm building and running all this on, it's DocForgestarted with a GST invoice generator and it's grown from there. Still early but it's showing up in Google, and that's more than it was 30 days ago.
If you're doing SEO on your own project right now what's the hardest part? Drop it in the comments.