Ferenc Fekete

Helping non-tech Founders transform Ideas into SaaS products @ VeryCreatives | Product Agency, SaaS & MVP Development | Startups

I've watched many startup founders fail at the same exact point: turning their validated idea into actual software.

They waste months (or even years):
→ Trying to hire the right developers
→ Burning cash on poor planning and execution
→ Second-guessing every technical decision along the way

Meanwhile, competitors move faster, investors demand traction, and the pressure to deliver keeps building more and more.

After watching this pattern destroy countless promising startups, we built VeryCreatives to fix it.

But here's what makes us different:

We don't just build your MVP and disappear. We're product people who think like founders, not just developers who code to spec.

👉 𝗩𝗮𝗹𝗶𝗱𝗮𝘁𝗶𝗼𝗻-𝗳𝗶𝗿𝘀𝘁 𝗮𝗽𝗽𝗿𝗼𝗮𝗰𝗵: We start by pressure-testing your assumptions before writing a single line of code. If the market doesn't want it, we'll tell you straight.

👉 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗺𝗶𝗻𝗱𝘀𝗲𝘁 𝗳𝗿𝗼𝗺 𝗱𝗮𝘆 𝗼𝗻𝗲: We build like it's our own startup, obsessing over user experience, scalability, and investor readiness from the first sprint.

👉 𝗙𝗿𝗼𝗺 𝗶𝗱𝗲𝗮 𝘁𝗼 𝗲𝘅𝗶𝘁 𝗮𝗻𝗱 𝗯𝗲𝘆𝗼𝗻𝗱: Whether you're at napkin sketch or Series B, we've been there. We've helped founders go from zero to acquisition, and we stick around for the entire journey.

For the past 14 years, we've built products for venture-backed startups, fast-growing scale-ups, and globally recognized brands like Red Bull, Nestlé, and Philips.

The startups we work with have:
✅ Launched investor-ready MVPs in under 90 days
✅ Secured funding from top-tier investors and VCs
✅ Scaled from first users to thousands of paying customers
✅ Successfully exited to strategic acquirers

Got a SaaS idea that's been sitting in your head for months? 
Let's map out your 90-day path to launch → https://verycreatives.com/book-a-call

Co-Founder

At VeryCreatives, we are a team of expert developers who create powerful SaaS apps that solve problems and drive growth for founders with initial funding. We believe in empowering our clients with innovative software that helps them achieve their goals and stand out in their industry.

Our audience consists of driven and ambitious founders who have just received initial funding for their startup. They are looking for a software development partner who understands their vision, can help bring their ideas to life, and deliver results that will help them achieve their business goals.

Founders with initial funding have a pressing need to build their product quickly and efficiently to maximize their chances of success. At VeryCreatives, we understand this need and are dedicated to creating high-quality SaaS apps that not only meet their requirements but also exceed their expectations. We are committed to delivering value and results that help our clients succeed.

VeryCreatives stands out in the market for our ability to deliver high-quality, innovative solutions that meet the needs of our clients. Our unique approach to software development, coupled with our expertise and commitment to excellence, is what drives us to provide outstanding results to our clients.

Industries our clients operate in, using the SaaS products we've built: 
- Digital marketing, Event marketing & Influencer marketing SaaS
- Foodtech & Delivery 
- Fintech, Banking & Investments
- 2-sided marketplace platforms
- Agriculture & Livestock management
- Packaging compliance & Waste

Markets we cover: UAE, EU, UK, US.

Your product isn't the problem. Your budget split is.

I've built countless SaaS products and apps over the past decade for some of the biggest brands in the world. Here's the biggest mistake I see first-time SaaS founders make that kills their product:

They map out their entire product budget... and allocate 100% of it to development.

They're planning to build the full product, launch it, then HOPE customers show up.

But the problem is, a good product is only 50% of the equation. The other half is getting it in front of the right people (which costs a lot of money too).

Especially in B2B, you'll need to spend some cash to speed up your learning curve and learn:

👉 Which channels work
👉 What messages resonate
👉 What makes your ideal customers actually convert

Some founders ignore this until it's too late. And by that time, they've burned through their development budget and launched something that MIGHT be great without anyone actually knowing it exists.

That's why whenever we work with clients, we often help them adjust the product scope before building anything out. Because we want to free up budget for marketing, user acquisition, and proper positioning so they can actually get customers and scale the business.

You could have the best product in the world. But if nobody knows it exists, it won't mean a thing.

Before you finalize your budget, ask yourself:

What's my plan to get 100 people to see this?

Helping startup founders & innovation labs validate and scale ideas into exit-ready products @ VeryCreatives | 🔥 Two decades in tech

You created your own bad developers.

I have seen this pattern too many times.

Founder says:

"My devs are slow"
"They do not get it"

Then we look closer.

And see a decision vacuum the team is trying to survive.

There are three calls only you can make as the founder.

If you dodge them, even a strong team will look useless:


👉 Decision 1: Who is our primary user right now?

One founder I worked with tried to serve agencies and tiny solo founders at the same time.

Sales promised custom features to big accounts, product built self serve onboarding for tiny ones, devs got whiplash.

Nine months of work, nobody truly happy.


👉 Decision 2: What is the next business outcome we are willing to bet on?

MRR from a segment, activation rate, expansion from existing customers.

If this is not written down, every feature feels urgent.

You ship a lot of stuff and still cannot answer why revenue or usage is flat.


👉 Decision 3: What constraints are non negotiable?

Time, budget, compliance, integrations.

If these move every week, scope will quietly double and your v1 will arrive six months late.


Which of these three have you been dodging?

Most failed software projects don't fail at the finish line.

They fail in week 2, when the team realizes the core feature can't actually be built.

That's why one of the smartest things you can do as a SaaS founder, before writing a single line of code, is build a proof of concept.

Not a full product or MVP. Just enough to answer one question: "Can we actually build this thing?"

We've gone through this exact process hundreds of times for both our clients and our own internal tools.

Here's how it works:

👉 Proof of Concept (PoC): Does this work technically?

This is where you test your riskiest assumption. Can it even be built the way you imagine? It's not going to be pretty, and it's not public-facing. But it's real.

Skip this, and you're three months into development before realizing your AI feature needs data you can't legally access.

👉 Prototype: What will it look and feel like?

Map the user flow, add just enough UI to walk someone through it, and start shaping the product experience.

Skip this, and your dev team builds something technically correct that no user can figure out how to use.

👉 MVP: Will people actually use and pay for it?

Now you're testing the market. You've built something lean and functional to prove there's demand and that your positioning makes sense.

Skip this, and you spend 18 months perfecting a product nobody asked for.

A good proof of concept helps you spot technical roadblocks early and gives stakeholders the confidence that your idea is real.

It's faster (and cheaper) to find the cracks now than to rebuild everything later.

What's the riskiest technical assumption you've had to validate before building?

Your first 10 customers are friends.

Your next 100 are stress tests.

Most MVPs crack right there.

And it's rarely the thing you're watching for.

Not because of one big bug.

Because of 4 invisible gaps almost every founder forgets:


1. Role and permission basics

A single login is fine at the very start.

Then a bigger account asks "Can my team have different access levels?"

If the answer is no, that deal quietly dies.

👉 By month 6, if you don't have this, you'll start losing deals you never knew you lost.


2. Bulk actions for power users

Clicking one by one feels fine with 10 records.

At 1,000, people hate your product.

They will export to Excel and never come back.

👉 By month 6, if you don't have bulk edit or export, your power users are already halfway out the door.


3. Password reset that does not melt support

In the early days, you just "help people manually."

At 150 accounts, your inbox turns into "I cannot log in" hell.

👉 By month 3, if you don't have a clean self-service reset flow, your support load will bury your roadmap.


4. An internal admin tool

If every tiny change needs a developer, your roadmap will stall.

You cannot build new features and play support at the same time.

👉 By month 9, if you don't have a simple internal panel, your engineers are stuck doing data cleanup instead of shipping.


Audit your stack against this list. What's missing?

I Spent 6 Months Building a Product Nobody Wanted. Then Buffer Launched for $5.

Around 2010, we worked at a media agency.

We saw the chaos every day: social media posts bouncing between marketing, legal, and clients. Approvals lost in email threads. Deadlines missed.

So we decided to build the solution ourselves.

We went all in:

• Multi-tenant account management
• Multi-platform posting (Facebook, Twitter)
• Custom approval workflows
• Notifications, previews, media library
• Analytics dashboard
• Unified posting interface

Six months of nights and weekends. Thousands of lines of code.

We never talked to a single customer.

We thought we knew exactly what agencies needed. We worked in one. We lived the problem.

That was the trap.

While we were perfecting our approval flow logic, Buffer launched with a single post scheduler and a $5 beta signup.

They validated demand before building anything else.

We validated nothing. We just built.

Here's what I learned the hard way:

👉 Working in an industry doesn't mean you understand the market

Your experience is one data point. Not a business case.

👉 Features don't prove demand

Nobody cares about your feature list if they never asked for it.

👉 Skipping customer development is not a shortcut

It's the longest, most expensive path to failure.

The product died quietly. No dramatic crash. Just silence.

If you're building something right now, ask yourself:

Have I talked to 10 people who would pay for this?

If the answer is no, close your IDE and pick up the phone.

Build your online presence, grow your network, enhance your professional image, get noticed, and unlock exciting career opportunities.

12 years in management. I forgot what building felt like.

In 2025, I started coding again. Now I ship every morning using AI tools, working alongside a non-technical cofounder, building Sucana from scratch.

I've spent 24 years in product development. I've built enterprise software used by 100,000+ employees and consumer apps used by 3M+ users. I know what it takes to build at scale, secure, maintainable, production-grade.

But I also know how to move fast. Ship lean. Validate early. Launch in days, not months.

Right now, I'm building in public. Documenting the journey. Sharing what it looks like to start again in your 50s with clarity, patience, and focus.

I enjoy vibe coding, tech trends, and gardening.

Vinod Sharma

I work at 4 am 
Because during the day 
I work with these incredible people.

My 9 to 5 job is fulfilling. 
I lead large initiatives & teams.
I help manage complex situations. 

I indirectly contribute to patient care. 
It is meaningful work.

But I also have my own ideas. 
My own initiatives and projects. 
Things that have been sitting in the back of my mind for years.

Working at 4 am gives me that space.
It lets me explore what is possible. 
It lets me stay sharp technically.

4 am works for me. 
It might not work for you.
But somewhere in your schedule, there is a window.

Find it. 
Protect it. 
Start building.

Use it to work on those ideas 
That you have been sitting on.
Who knows where they will lead you.

What is your window for your own dreams?

Building Sucana while working full-time using Claude Code. Back to coding in my 50s after 12 years in management. I enjoy vibe coding, tech trends and gardening.

Clawdbot became one of the hottest AI tools overnight.
Yesterday, it went through every founder's nightmare. 
All in 24 hours.

First, Anthropic sent a trademark claim. 
The name "Clawd" was too similar to "Claude."

They rebranded it to Molt.

But during the rename, the founder made a critical mistake.

Between releasing the old name and claiming the new one, 
Crypto scammers grabbed both the GitHub organization and the X handle.

10 seconds. That is all it took.

These scammers then used the hijacked accounts to 
start pumping fake $CLAWD tokens to tens of thousands of followers. 

The token hit $16 million market cap before people realized it was a scam.

Meanwhile, security researchers found vulnerabilities. 

API keys, bot tokens, OAuth secrets all accessible. 
Hundreds of publicly exposed instances. 
Full conversation histories visible. 
Prompt injection via email.

All of this in 24 hours.

One oversight.
One mistake. 
One gap. 

That is all it takes.

4 am
Every day.
Including weekends.

Two cofounders in our 50s.
Just showing up and building.

What’s your building routine?

Just wrapped up a 5 hour focused coding session.

Shwet Prakash was with me on Zoom, which helped me stay locked in and avoid distractions.

I ran two Claude Code sessions side by side, switching when one went into coding mode.

How’s your Sunday going?

No alternative text description for this image

For the last few weeks,
I’ve been in extreme focus mode.

I code.
I garden.
I eat and sleep.
Then repeat it daily.

All while leading two projects in my 9–5 job.

No X spaces.
No daily posts.
Not recording videos.

Just Claude Code coding.
Long brainstorming sessions.
Deep ideation and architecture work.

This momentum cycle has been extremely fulfilling.

Curious how others structure their focus while balancing leadership, building, and life.

It's 4 am.
I am in my 50s.
Coding in 3 windows.

1. Sucana waitlist
2. Sucana main application 
3. Personal CRM using Moltbot running on AWS

That third one is wild.
I just send messages on WhatsApp. 
And Moltbot does the coding and deployments.

I did not code for 12 years.
Now I code every day with AI.

AI coding brought me back to building.
It can do the same for you.

If you stepped away from code, this is your moment.

But remember:

Start slow.
Take precautions.
These tools can do real harm 
If you are not careful.

What's stopping you?

It’s 4 am.
The post about extreme focus
ended up becoming a distraction.

Replies.
Views.
Numbers.

So I made a call.
No X for the next 4 hours. 
Back to building.

Happy Sunday everyone.

4 am Wake up & start building.
5 am Sucana team meeting.
6 am Long drive sunrise.
7 am Building again.
9 am Gardening.

Early starts.

What you do on weekends 
separates you from 
those who only talk 
about building.

After 12 years in management, I forgot what coding felt like. 
Now I build every morning with someone who can't code. 
And it's the most productive I've been in my entire life.

We are two cofounders in our 50s.
Working together every morning.

Different backgrounds.
Different strengths.

I’m deeply technical.
Code, architecture, implementation.

Virgil Brewster is non-technical.
But strong in UX, positioning, and marketing instincts.

That contrast has become our biggest advantage.
He pushes for simplicity, flow, and user experience.
I translate that into Sucana using Claude Code.

There's something about doing this in your 50s. 
You stop overcomplicating. 
You know what matters.
You show up and build.

What’s new for both of us is this phase.
Building something from scratch again.
A new product.
A new rhythm.
A new hope.

We show up every morning.
Decide.
Build it.
Repeat.

This feels different.
And in a good way.

If you’re building with a cofounder, I’m curious,
what skill combinations have worked best for you?

Planted new flower seeds and built new flower beds.

These will bloom a few months from now.

Gardening is one of the best ways to learn patience.

You put in the work for months without seeing results.

Then one day, things start to bloom.

I’ve learned this is just as true when building 

a career,
a side hustle,
or a micro SaaS startup.

Most of the work happens quietly, long before anything is visible.

If you stay consistent long enough, the results eventually show up.

Just migrated from

ClawdBot → OpenClaw.

Here's how (takes 15 minutes):

––

1. First, back up your data:
tar -czvf clawdbot-backup.tar.gz ~/.clawdbot ~/clawd

––

2. Stop the old daemon:
clawdbot daemon stop

––

3. Install OpenClaw:
sudo npm install -g openclaw@latest

––

4. Install the new gateway service:
openclaw gateway install openclaw daemon start

––

5. That's it. OpenClaw auto-migrates everything:

Config → ~/.openclaw/
WhatsApp session ✅
Memory files ✅
Sessions ✅

Old paths get symlinked so nothing breaks.

––

6/ Verify it worked:
openclaw status

Then message yourself on WhatsApp.
Your bot is now running OpenClaw 🦞

––

7/ Clean up old service (optional):
sudo systemctl disable clawdbot-gateway.service sudo systemctl daemon-reload

The lobster has molted 🦞

taplio

The Battle

Ferenc Fekete

Vinod Sharma

Followers

Posts

Engagements

Likes

Performance ScoreFerenc Fekete's LinkedIn Performance

Performance ScoreVinod Sharma's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Ferenc Fekete

Vinod Sharma

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Ferenc Fekete's LinkedIn Performance

Performance ScoreVinod Sharma's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreFerenc Fekete's LinkedIn Performance