DEV Community: danieelatu

If this doesn't kill your app, then I’m damn sure it will help: How a rebrand turned ChatGPT into my #1 referral source.

danieelatu — Sun, 25 Jan 2026 15:11:55 +0000

14 days ago, my project was called Copywritee.

I’d spent a year building it. I had some authority, a bit of awareness, and some sweat equity. But the data was screaming one thing: The name was a bug, not a feature, which i now know but changing a domain name could result to some dangerous consequences like ____________________________ yeah. a flat line of traffic

The Dilemma
People saw the name and assumed I was building a ChatGPT wrapper for blog posts. In reality, I was building a heavy-duty OCR engine that converts:

Messy, handwritten cursive tables → Formatted Excel files.

Handwritten notebooks → Word Documents.

Live PDF editing and cloud storage.

I was at a crossroads. Do I stick with "Copywritee" (after all, Apple doesn't sell fruit)? I use that to deceive myself, but then again, Apple has earned its name with years of work, so that's off the comparison table. Or do I risk a year of SEO work to pivot to something niche?

Well...
I killed the old name and rebranded to NoteOCR. I handled the 301 redirects, updated the metadata, and braced for a crash.

Instead, my traffic doubled in 7 days. (I expected a crash)

Why it worked (The Technical "LLM" Twist)
The most surprising part? My #1 referral source isn't Google, it's ChatGPT. Here is why the rebrand triggered the "LLM Referral Engine":

Semantic Clarity: "Copywritee" was abstract. NoteOCR is high-intent. When an LLM crawls my site, it no longer has to "guess" my niche. My "relevance score" for handwriting-to-text queries shot through the roof.

The Metadata Match: I stopped trying to rank for broad terms like "AI Writing" and went deep on "Handwritten OCR." By aligning the domain name with the primary

and description tags, I became the "Authoritative Answer" for ChatGPT Search.

Directory Synergy: I listed on specialized AI directories. Because the name is surgical, the backlink profile became much more "topical," which tells AI models exactly when to recommend me.

The Lesson for Founders/Devs
We often get attached to our "clever" project names. But if your name forces you to explain what you do, it's a bottleneck. I killed a year of branding to let the product breathe.

The result? A 2x jump in traffic in a week and a product that finally "makes sense" to both humans and AI.

Check out the new engine: noteocr.com

Why "Manual Data Entry" is a Bug, Not a Feature in 2026

danieelatu — Tue, 20 Jan 2026 17:13:10 +0000

Tags: #futureofwork #ai #productivity #automation #startup

We are well into 2026, and yet, I still see some of the smartest people in finance, law, and healthcare spending 4 hours a day doing something a machine should have solved a decade ago: Typing data from paper into Excel. In the early 2020s, we were promised that the "paperless" days was here. But the reality is that unstructured data—handwritten notes, messy tables, and faxed forms—is still the lifeblood of many industries.

I don't blame anyone for that, most people feel it is simply quicker and easier to write on paper than to type on a computer in the moment. The problem arises later: that handwritten data still needs to be stored, transferred, and duplicated. This leads to unnecessary hours spent transcribing handwritten content into a polished, formatted document.

The Task-Replacement Reality
The most heard phrase in 2025 is, "AI is coming for our jobs." Most people think AI is a giant wave coming to replace their entire career. But AI isn’t replacing jobs all at once; it’s quietly replacing tasks.The real "Future of Work" isn't about robots in suits. It’s about Agentic AI—systems that don't just "read" a document, but actually understand its geometry. When I started building NoteOCR, I realized that the goal wasn't just OCR (Optical Character Recognition).It was Reconstruction.

The New Standard: Human-Centric Automation
If a human has to spend 30 minutes fixing a bad AI export, the AI has failed. In 2026, productivity is no longer about doing more, it's about doing less by offloading "low-value" cognitive labor.

We are moving through three distinct eras:

The Manual Era: Type, check, type, repeat.

The Basic OCR Era: Scan, get a messy text dump, and spend an hour cleaning it.

The NoteOCR Era: Upload handwritten content (including tables), let the engine perfectly format your handwritten text, convert it to a document, reconstruct the table geometry, and hit "Export."

As AI absorbs these repetitive, rule-based tasks, the role of the knowledge worker is shifting. We are moving from being "data operators" to "data architects." We are now here to oversee the AI, verify the 97% accuracy, and move straight to the strategy—which is where the real value lies. Manual data entry is a relic of the past. It’s time we treat it like the bug it is.

I’d love to hear from you: How much of your "daily grind" is still just moving data from one place to another?

Convert handwriting to text - how I built a handwriting recognition platform

danieelatu — Wed, 09 Apr 2025 01:58:22 +0000

We've all been there — scribbled notes, classwork, ideas on paper that we wish we could instantly convert into editable, clean text without spending hours of typing. That pain inspired me to build something I believe many people could find useful: a web platform that converts handwritten notes to digital text, and then lets you edit, format, and download them just like you'd do with MS Word or Google Docs.

🔧 What It Does
My app allows users to:

Upload handwritten images
Convert them into editable text using OCR
Edit the output in a document editor (like a mini Word processor)
Save, export, and manage documents easily

Whether you're a student digitizing class notes or a professional turning quick sketches into polished reports — this tool bridges the analog and digital world.

🔍 The Stack I Used
Frontend: React + Tailwind CSS
Backend: Node.js + Express
Editor: Rich text editor integration (Onlyoffice)

🎯 Challenges I Faced
OCR Accuracy: Handwriting is tricky. I had to experiment with contrast, image preprocessing, and different OCR models.

Document Editing UX: Making the editor feel fluid and responsive took time — especially getting text formatting to feel natural.

File Handling & Security: Ensuring uploaded images were safely stored and accessible only by the uploader.

✅ What I Learned

User expectations are high when it comes to text editors!
Performance optimization for OCR is key — image size matters.
UI/UX makes or breaks the user’s trust in the output . 🧠 Future Plans Add handwriting style training so it learns your handwriting better over time. Support for math notation (LaTeX output!)

If you're curious to test it or want to help contribute, feel free to drop me a message or leave a comment 👇
TRY IT OUT: Copywrite

Building this was both technically and emotionally rewarding. It's one of those projects where you're solving your own problem — and it feels great knowing it could help others too.