/// Services
Copy, design, code, and the audit that tells you which of them is costing you money. I do all four myself, so nothing gets lost in the handoff — and you brief one person instead of managing three freelancers who've never spoken.
/// The Four Services
Each one stands on its own. Together they cover everything between “nobody can find us” and “they find us and still don't buy.”
Pages that rank, and then actually convert.
I research the keywords your buyers actually search, audit the pages already ranking for them, and write every page myself — structured so Google can rank it and a visitor can act on it. No handoff between an SEO specialist and a copywriter.
Interfaces built around how people actually scan.
I design high-converting Figma pages and product screens around the way real users read, decide, and act. Because I wrote the copy first, the layout follows the message instead of the message being squeezed into a template afterwards.
The design, shipped exactly as approved.
I build what I designed in Next.js, wired to a headless CMS your team can run without me. Performance budget agreed upfront, SEO handled in the markup rather than bolted on with a plugin, and the repository handed over at launch.
The exact reason visitors leave, ranked by cost.
I read your pages the way your buyer does, back every finding with your own analytics, and rank them by what they're costing you. Then I hand over the rewritten copy and layout for the top ones — the report arrives with the fix attached.
/// Why It's All One Person
A writer hands a document to a designer who never spoke to them. The designer hands a file to a developer who invents the missing states. By launch, three people have each solved a different problem, and the argument the page was supposed to make has quietly disappeared.
I do all four myself. That's not a boast about range — it's the reason the page you approve is the page that ships.
One brief, read once
No translation between specialists
Consistent voice end to end
One person accountable
/// How a Project Runs
Most bad projects are not bad work. They are a client and a supplier holding two different pictures of what was agreed. So the process is built to make those pictures the same one, early, while changing them is still cheap.
Thirty minutes on the pages you already have, what you have tried on them, and what the numbers did afterwards. You leave with a read on where it is leaking whether or not we end up working together.
A document setting out what is included, what is deliberately left out, and where the review points fall. You approve it before a single page is written — almost every dispute later traces back to something nobody wrote down at this stage.
What your buyers actually search, which pages already rank for it, and what your own analytics say people do once they land. The brief comes out of your data — not out of an assumption about your market.
Work arrives at agreed review points rather than as one reveal at the end. Redirecting something in week two costs a conversation; discovering it at handover costs the project.
Figma files, the repository, CMS access, and the notes needed to run it. Nothing is held back as leverage — if we never speak again, everything still works and your team can still edit it.
Years of experience
Repeat clients
Successful projects
Happy clients
/// What It Gets Built On
A stack is a hiring decision as much as a technical one. Everything below is common enough that any competent developer can pick it up after I hand it over, which is the point — you should be able to replace me without replacing the site.
Layouts are approved here before anything is built, which is what stops “that is not what I signed off on” from surfacing at launch. The files stay yours, and any designer can open them.
Chosen partly because the hiring pool for it is deep. If you need someone else to extend the site in two years, you will be recruiting from a large field rather than looking for the one person who knows your framework.
Sanity, Contentful, or Payload. Content lives in a structured schema that can be exported whole, so moving platforms later is a migration rather than a retype.
WordPress and Shopify teams keep their admin. Switching platforms is a cost with no customer on the other end of it, and I would rather spend your budget on the pages that earn.
Industry
Testimonial
I have had a great experience working with him. We were working on a project about a saas app. He played a good role in the collaboration of copywriting and UI design. Recommended.
Founder, GoalFlow
We needed a website UI for Bangla Venture that looked professional and guided the user without friction. Hamidul, nailed the visual hierarchy. It’s a pixel-perfect design that perfectly captures what Bangla Ventures stands for.
Founder, Banglaventure
Titas joined the Growminion team to handle writing and design for our local SEO clients. He consistently delivers high-quality work, and we’ve had a fantastic experience working with him.
Founder, Growminion
Titas helped us design a product landing page for Peanela, and the experience was excellent. He understood our requirements clearly, delivered a clean and professional design, and maintained great quality throughout the project.
Managing Partner, Peanela
Got Questions?
No. Each one is sold on its own, and plenty of clients only ever need one. The advantage of taking more than one is that nothing gets lost between them — but that's an option, not a requirement.
If nobody can find you, start with copywriting. If they find you and leave, start with an audit. If you have a design but no site, start with development. If you're not sure, book a call and I'll tell you honestly — including when the answer is none of them yet.
Yes. I write, design, and build, which is why the strategy survives from the first keyword to the deployed page. It also means I take on a limited number of projects at a time, so availability is genuinely finite.
It depends on scope, and I'd rather quote properly than post a number that misleads you. A single landing page and a twenty-page site with a CMS migration aren't in the same bracket. Tell me what you need on a call and you'll get a fixed figure in writing.
Usually within one to three weeks, depending on what's already in progress. Audits can often start sooner because they need less of your team's time upfront.
Most of my work is with clients in the US, UK, EU, and Australia. Everything runs async by default with calls scheduled in your timezone, so the distance rarely comes up after the first week.
Blogs
