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.

Arpit Singh

GTM, AI & Outbound | LinkedIn Content & Social Selling for high-growth agencies, AI/SaaS startups & consulting businesses | Open for collaborations

Hi, I’m Arpit. I build growth systems by combining LinkedIn content, social selling, and GTM workflows.

I’ve been in marketing, ops, and GTM for 6+ years, with the last 2.5 years deep in outbound and social selling. 

In that time I’ve:
→ Worked with 50+ B2B clients across SaaS, fintech, and services
→ Scaled GTM engines inside agencies
→ Reported directly to 15+ founders and CMOs
→ Built outreach systems delivering 300+ replies per month
→ Fixed inbox placement from 20% to 90% in 10 days
→ Automated more than 10,000 touchpoints each month

Who I work with:
→ Founders making $20K to $100K per month who need predictable growth
→ GTM teams scaling sales and content but lacking systems
→ Agencies that want inbound and outbound working together

What I do:
→ LinkedIn content and social selling playbooks
→ Cold outreach and deliverability fixes
→ Trigger-based workflows across LinkedIn and email
→ Full GTM systems including automation, dashboards and SOPs

Currently, I’m a GTM Engineer at Content Path helping B2B brands turn content and outbound into one scalable growth engine.

If you’re looking to align content, outbound, and systems into a GTM engine that compounds over time, DM me.

Growth Strategist

At Huemor we build memorable websites for brands like yours that earn more customers, outshine competitors, and help recruit top talent.

After a website redesign, our clients typically experience:
+ 83% monthly website visits
+ 94% increased conversions
+ 91% leads generated

📞𝙉𝙚𝙚𝙙 𝙤𝙪𝙧 𝙝𝙚𝙡𝙥? 🗓
If you need help improving your current website, building a new one, or generating more organic traffic, we'd love to talk about it.

Get in touch by either...
Messaging me here on LinkedIn
Booking a free strategy session: https://bit.ly/4cHNIGc

One of the hardest parts of sending 20K emails/month?

Email infrastructure setup.

The situation usually looks harmless.

Replies slow down.
The opens still look fine.
Nothing is obviously broken.

So teams assume it’s copy.
Or personalization.
Or the offer.

But that’s rarely the reason.

This happens because email infrastructure doesn’t fail loudly.
It degrades quietly.

Mailboxes burn.
Reputation slips.
Deliverability drops before dashboards warn you.

That’s why I’ve trusted Maildoso for over a year.

It fixes the boring part of outbound. And that boring part matters.

What made me stick with Maildoso:

• 98%+ inbox placement, even to Outlook
• In-house SMTP. No resold nonsense
• IP rotation that keeps things clean
• Self-healing mailboxes so campaigns don’t just… die
• $1.80–$2.50 per inbox, domains included

What Maildoso gave me wasn’t hacks or hype. 

It gave me predictability.

Outbound stopped feeling fragile. 

Replies started making sense again.

If you’re scaling cold email and replies dip without a clear reason…

It’s worth checking whether the problem is really email copy… 

or the infrastructure underneath it.


P.S. See the link in comments to check it out for yourself

I’ve been using HeyReach for 2+ years now.
What I’ve noticed every single time:
They ship fast when users ask for something.

Creators ask.
Customers ask.
Updates show up.

That’s the kind of product behavior GTM engineers respect.

A few weeks ago, they rolled out 2 updates.

Nothing flashy. But if you run LinkedIn outbound seriously, you’ll get why these matter.

1️⃣ Manager role

Access control used to be annoying.

You either gave someone Admin access 
or locked them down so much that they couldn’t really operate.

Now there’s a proper middle layer.

Managers can work inside external workspaces, run campaigns, manage users, see what matters without touching billing or permission settings.

If you work with agencies, contractors, or shared GTM teams, this removes a lot of unnecessary coordination.

2️⃣ Workspace API

This one’s clearly built for GTM engineers.

It covers the boring parts of scaling LinkedIn outbound
the stuff you normally fix with spreadsheets and Slack messages.

You can now:

• Create and manage workspaces
• Pull users by role or invite status
• Invite Managers, Admins, Members
• Create API keys per workspace
• Connect it with Make, Zapier, n8n, MCP, Public API

Which matters when you’re onboarding clients or spinning up new GTM pods regularly.

These aren’t exciting updates.

But they make your outbound setup easier to live with.

And that’s usually a sign the product is built for real operators.


Do you use HeyReach.io in your GTM stack or workflow?

I’ve been using Trigify.io for 1.5+ years now.

Now, I’ve been tracking 25+ LinkedIn profiles on it, mostly for my clients.

And one thing is very clear to me:

Posting on LinkedIn isn’t the hard part. 
Tracking what happens after is.

Most people stop at “posting consistently”.
That’s where the real problem starts.

What usually goes wrong...

1. Everyone tries to create content for their ICP
– very few do it consistently
– even fewer attract the right people

2. Some posts get engagement
– likes
– comments
– profile visits

3. And then… nothing
– no tracking
– no follow-up
– no system

That’s wasted INTENT.

What actually works (when you track it):

1. Lead magnet → warm outbound

→ Post a lead magnet
→ Track who engages with it
→ Enrich those profiles
→ Use that list for outbound

You’re no longer cold. You’re starting with context.

2. Competitor & creator engagement

→ Track engagement on competitor posts
→ Or people consistently posting in your niche
→ Scrape those interactions
→ Enrich the data

Now you’re reaching out to people who are already active in the problem space.

3. Keyword-based intent signals (underrated)

→ Track engagement around keywords like:

   ~ “intent signals”
   ~ “GTM Engineer”
   ~ “RevOps”

→ Build lead lists from those conversations

→ Reuse them for:
   ~ outbound
   ~ content ideas
   ~ account research

Same signal. Multiple plays.


Why I’ve stuck with Trigify.io, it’s not because it’s flashy. But how it turns LinkedIn activity into usable intent.

Post-level tracking.
Profile-level monitoring.
Keyword-level listening.

And now, workflows make this operational. 

Instead of exporting data, stitching tools, and manually following up, you can:
- track engagement
- enrich profiles
- route data where it needs to go
- trigger next steps automatically

They’ve also been adding integrations around enrichment, sequencing, and data sync, which makes these workflows practical in real GTM setups.

But the core idea stays the same: 

If you’re already creating content and doing outbound, you should be tracking who’s raising their hand.

Otherwise, you’re guessing. And guessing doesn’t scale.

This is the difference between posting content and building a system.

Do you actually know who’s engaging with your content?

taplio

The Battle

Ferenc Fekete

Arpit Singh

Followers

Posts

Engagements

Likes

Performance ScoreFerenc Fekete's LinkedIn Performance

Performance ScoreArpit Singh's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Ferenc Fekete

Arpit Singh

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 ScoreArpit Singh's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreFerenc Fekete's LinkedIn Performance