Find me on https://lovable.dev/@lazarjovanovic

Lazar Jovanovic

Starting tomorrow I’m doing 28 days of Lovable.
And yes, I’m giving out credits at the end.

And here’s why I am doing it.

About a year ago, I was struggling more than I let on.
Not stuck because I was lazy.
Not stuck because I wasn’t smart enough.

I simply didn’t have a system to fall back on when things got messy.

So I built a few, and now I want to share them with everyone.

Over the next 4 weeks, I’m breaking down how I actually build with Lovable - from ideas → systems → shipping → autonomy.

Not just what I do.
But why it works.

At the end, I’ll be giving out Lovable credits to the best project built during the challenge. But the criteria on what I think is best is completely different from the usual scoring systems. 

You’ll have to stick around and follow along for that one! 

Also, let me be very clear:
> Credits alone won’t make you a better builder.
> Tools alone won’t make you a better builder.
> AI alone won’t make you a better builder.

What I actually want people to walk away with is:
a new way to think
a way to structure their work
a way to remove themselves as the bottleneck
a way to execute anything they decide to build next

That’s (hopefully) the real prize.

If you’ve ever felt like you’re “not technical enough”, or you start projects but don’t finish, that tools feel magical but unreliable and AI helps… but not consistently…

This series is for you. 

At the end, all the videos, prompts and lesson materials will be inside this companion app. My hope is that you find it useful and then also send it to someone you care about. 

Let’s build something Lovable together.

GTM AI Coding Engineer at Lovable | L5: Diamond Certified

I almost talked myself out of doing this event...

Standing on a stage. 
Running a room. 
Being “the guy” responsible for the energy, the flow, the outcome. 

I’ve done and built a lot of things, but this was different. 

This was public. 
Human. 
Unscripted.

But in reality, that fear was the point.

Last Friday in Miami, Sabina Shuminov from CGU hosted a Lovable buildathon, and it ended up being one of the most fulfilling experiences I’ve had in a long time.

Yes, AI is moving fast. 
Yes, the tools are getting absurdly powerful.

But after watching a room full of people of first-time Lovable users, builders, designers, non-technical founders and engineers, curious minds sit together, talk, laugh, get stuck, help each other, and create… it became obvious again:

Nothing beats human-to-human interaction!

That moment when it clicks; “Wait, I can actually do this”, never gets old.

I was nervous going into it. 
I hate being on stage more than I’d like to admit. 

And to make things even more intimidating, I had to follow an absolutely killer fireside chat by Unnat Bak from Revscale AI, who crushed it so hard it felt borderline irresponsible to put me up next.

But that’s the lesson I keep relearning: The things that scare you a little are usually pointing at the exact direction you should move in.

I walked away with new friends, new energy, and a much deeper belief in what we’re building at Lovable.

And while I don’t love singling people out, meeting Teresa Hill in person, winner of S2 of She Builds was a highlight. Someone I’ve admired from afar, now face-to-face, and I have zero doubt she’s onto something big.

If you’ve been sitting on an idea…
If you’ve been waiting to feel “ready”…
If fear has been quietly calling the shots...
Build the thing anyway.
What’s actually stopping you?

Smarter -> Better -> Stronger ->>> Lovable ❤️

I don't use Facebook and Instagram. 

If you want to follow what I do every day... There's only one place in the world that captures that better than any other - https://lnkd.in/dtGCh7UH

Follow me, I need to beat Elliot Lindberg 🤫 

P.S. Claim a cool username today, vibecodeking is available (don't ask me how I know haha)

What's stopping you from vibe coding like this!?

Most people already gave up on their New Year’s resolution.

Not because they’re lazy.
Not because they don’t want it badly enough.

But because January is built on pressure, not systems.

Here’s the part nobody talks about:
</> Starting something new in January feels performative.
</> Starting something new in February feels intentional.

By now:
</> the noise has died down
</> the motivation posts stopped
</> reality kicked in

Which makes this the best time to begin.

I’m about to start something that’s not about motivation at all.

It’s about building systems instead of hype, making progress without burning out, learning how to start, stop, and restart properly.

If you’ve been telling yourself “I’ll start again later” - this is later.

More info coming soon. 👀 


--
P.S. Link to sign up is in the comments

Lovable: You can now queue your messages!

Me: ☕ 

Lock. In.

Every product you use exists because someone got annoyed enough to fix something for themselves.

That is not a cliché. 

That is literally how this works.

Welcome to Day 1 of 28 Days of Lovable. Before we touch a single line of code or an AI builder, we have to find a problem worth caring about. 

And here are the places to find those ideas:

Your search history is a gold mine.

If you are struggling with something right now, chances are thousands of other people are too.

Open your browser. 
Look at what you have been Googling in the last 30 to 90 days. 
You will find things like:
- Best finance tracker
- PDF compressor
- Tool for X but simpler

If you searched for it, you wanted it badly enough to stop what you were doing. That is signal. 

Now ask yourself: What annoyed me enough to search for this?

Usually, it is because existing tools are bloated, too expensive, or too slow. This is where your idea sharpens. You are not building a tool; you are removing friction.

To move forward, turn your problem into a story:

"I want to build a web-based tool for [who] who struggle with [specific problem], because existing solutions [what they do wrong]. This tool will feel [simple / fast / focused] and solve [one core thing] really well."

By the end of today, you should have one real problem from your own life and a short idea story written in plain English. 

No code yet. 
Just clarity.

For more resources on how to find good ideas, catch the full Day 1 lesson at https://lnkd.in/eWZShRpu

February is usually the worst month of the year.

The hype is gone.
The weather sucks.
The “new year, new me” energy is dead.

Most people are tired, behind, and quietly disappointed.

But that’s exactly why February can be the best month to start something.
And doing it loudly and publicly.

Not fueled by motivation. But discipline to show up daily. 

I’m putting something together that’s built for this moment, when the noise is gone and reality is back.

If you want to actually do something this year this is a good time to lean in.

February doesn’t have to be the month you fall behind.
It can be the month you quietly get started the right way.

I’ll drop the details tomorrow.

But if you want early access, you can sign up here:
https://lnkd.in/eqxZMGFa

Open article: 28 Days of Lovable by february.lovable.app

PSA reminder for everyone building today!

Stop trying to sound smart. 

When most people start building an app, their brain locks up because they think they need to sound technical, precise, and professional. 

But clarity doesn't come from structure. It comes from saying the thing out loud. 

For Day 2 of 28 Days of Lovable, we are throwing out the formal problem statement and replacing it with a story. 

If you can't explain your app to another human being, no AI is going to save you.

To move from idea to action, answer these three questions with zero jargon:

1. What problem am I actually trying to solve?
Don't use words like optimize or improve. Describe what is broken. If you are caring for a parent and feel lost juggling medications and portals, say exactly that. That is real and specific.

2. Who is this for?
Not users. Not people. Who is the specific person struggling with this right now? 

3. How should the solution feel?
This is the part most people skip, but it is your direction. Should it feel like a quiet mountain cabin or a high-speed cockpit? Use metaphors. Taste is your primary filter for design.

When you answer these, you shift from having an idea to understanding an experience. This becomes your first prompt. 

In Lovable, you can take this story into Plan Mode to generate an editable blueprint. You go from brain dump to execution without losing momentum.

You don't need a perfect framework to begin. You just need to be honest about what hurts and how relief should feel.

Catch Day 2 at https://lnkd.in/eWZShRpu

Pure gold! Felix Haas Liv Törnberg and Isaak Fabien Sundeman once again demonstrate that Lovable team is not just good at creating amazing software! 

https://lnkd.in/eKuHE6v8

Open article: Lovable on Instagram: "What is bro doing in the meeting pod 😂 #tech #startup #office #design" by instagram.com

Lovable on Instagram: "What is bro doing in the meeting pod 😂 #tech #startup #office #design"

Here to confirm that Lovable writes 100% of my code as well 😁

Founder @ Acquirafy.com | Helping early-stage founders build, launch & scale brands to predictable revenue. GTM Advisory. Launched dozens of brands & driven millions in revenue. | Ex-Trustpilot, Innocent Drinks, Accurx

Who wants a free website?

I'm looking to up my vibe coding level from L3: Gold. Lazar Jovanovic shines bright like an L5 💎 and thanks to him shared the news about this great new Lovable feature. But really I'm looking to hone my vibe coding skills as I build out my own portfolio of businesses. So I'm offering to build a website for someone, (or a basic app MVP) and film the process. Happy to look at names, logos, domains etc, if needed.

So if you want one, drop a comment about what you want built. I'll choose one and do my best to bring your vision to life.

Anyone in Miami area, join me in a few weeks and let's build something Lovable!

Strategic Partnerships | 18+ years in Sales | Impact Driven Events | Connecting Giants and Unicorns

New Year, New Vibe! Excited to announce our partnered event between Lovable and Connecting Giants and Unicorns -Vibe to Value -Sales and Marketing Buildathon 👩🏻‍💻 👨‍💻 💰 !

We are leveling up the #CGU experience with a new layer to our usual format-starting with a dynamic panel #discussion, moving to a 'Lovable Fundamentals' #workshop, and wrapping up with a hands-on #Buildathon!

 📅 January 16th 12:00PM, Wynwood

Here is what to except:
🎙️Fireside conversation: “Building AI-Powered Workflows for B2B Sales and Marketing”

Featuring:
Lazar Jovanovic – Lovable’s first Vibe Coding Engineer
Unnat Bak – Founder & Chief AI/Product Officer, Revscale AI

Dive into how AI is transforming #sales and #marketing workflows, bridging creativity and code through next-gen tools and automation.

💻 Hands-On Buildathon: From Idea to Working Product with Lovable
Roll up your sleeves and build it yourself with live guidance and support
 
💡 Bring your Sales/Marketing goals for 2026 and create your own tools to get them!  

🧾  Here is a partial list of what you can build:
⚪ Sales landing pages
⚪ Lead generation tools
⚪ Marketing dashboards
⚪ Referral Portal -All without writing a single line of code!

 🎯 Walk in with an idea — walk out with a working product tailored to your #2026Goals!

No coding experience required—just bring curiosity , your laptop and a willingness to build.

 ✨ Ready to turn your vibe into value?

🔗 Seats are limited — so mark your calendars and save your spot today!

Bro is already changing the world at just 18 years of age. 

I am humbled, amazed and honored to be able to say I work with this guy 💪❤️

The future isn’t predicted, it’s built🔥 Hear from top startup ecosystem talent on what’s coming next and the skills that matter. 

Elliot Lindberg 
Max Larsson 
Charles Maddock

With a solid foundation as an Oracle NetSuite Consultant, my focus at NetSuite revolves around driving strategic solutions and gap remediation to address our clients' most pressing challenges. We, as a team, have successfully collaborated with clients across various sectors to enhance their operational efficiency and align their business processes with industry standards.

My proficiency in Celigo Integrations and MVC, honed through impactful project management and solution architecture roles, empowers me to design and implement complex ERP systems tailored to the unique needs of each client. This dedication to client success is bolstered by a NetSuite Certified SuiteFoundation and a passion for continuous personal and professional development.

Sabran Hameed

Your expensive NetSuite might not be broken.

I see this constantly.

A company invests $200K in an ERP. Six months later, the finance team is drowning in manual workarounds. The warehouse manager is running a shadow system in Excel.

Everyone blames the software.

But when I dig into the original requirements, I find the real ghost.

The implementation partner asked what the system needed to do.
No one asked how the people actually worked.

I remember watching an accounts payable clerk spend 30 minutes every morning manually copying vendor data into a spreadsheet. She thought NetSuite couldn't handle the bank format.

It took two clicks to fix. The feature was already there.

She had been wasting hours of her life because the implementation focused on technical configuration instead of human workflow.

The system was working exactly as designed.

It just wasn't designed for the people using it.

You don't need new software. You probably just need to have the hard conversations about process that you skipped the first time around.



#NetSuite #ERP #BusinessProcess #DigitalTransformation #WorkflowOptimization

undefined undefined

Oracle Cloud Infrastructure 2025 AI Foundations Associate (1Z0-1122-25)

Oracle NetSuite AI Foundations Associate

NetSuite Certified Administrator

NetSuite Certified Financial User

Communication Foundation

Effective Listening

Interpersonal Communication

SKILLED

Accounting Foundation

NetSuite Advance Revenue Management

NetSuite Certified SuiteFoundation

Project management 

MBCS

Project Management Professional

Gap Remediation Leadership: Drive strategies to address client gaps, fostering agreement through effective communication and consensus-building.

Strategic Solution Design: Employ strategic decision-making in crafting solutions and architectural recommendations to meet client needs.

Client Collaboration: Collaborate closely with clients to identify and resolve their most critical challenges, prioritizing their success.

Leading NetSuite Practices: Guide clients and partners in implementing leading NetSuite practices, ensuring alignment with industry standards.

Complex Solution Architecture: Architect solutions for intricate business requirements, leveraging configuration, integration, and technical components in partnership with our Technical Services team.

Subject-Matter Expertise: Develop expertise and thought leadership, working with Product teams to ensure effective adoption of new features and capabilities.

Detailed Requirement Definition: Define precise functional requirements for automations, integrations, and data migrations, ensuring alignment with client objectives.

Technical Collaboration: Collaborate with technical teams to design and unit test automations and integrations, ensuring quality and reliability.

Quality Assurance: Perform quality reviews of deliverables developed by team members, providing valuable feedback and guidance.

Continuous Learning: Pursue ongoing product knowledge enhancement and relevant certifications to stay updated on industry trends and best practices.

Senior Principal Consultant

Senior Oracle NetSuite Consultant

Some of the responsibility covers:
•	Manage the implementation life cycle in coordination with the project team of the customer and deliver within the budget and time frame.
•	Manage customer expectations and ensure customer satisfaction.
•	Creating project plans, monitoring project progress, and preparing project progress reports.
•	Gathering, analyzing, and documenting customer business process requirements.
•	Preparing solution specifications and demonstrating the blueprint of the solution to the customer based on their requirements.
•	Managing HCM SuiteApp product development with multiple legislation incorporation.
•	Implementing the ERP/HCM software to best meet the customer business process needs.
•	Customer training.
•	Promote consultancy services to existing customers and generate consultancy revenue.
•	Preparing pre-sale demonstrations and presenting solutions to prospects.
•	Responding to RFP and RFQ’s.

Oracle NetSuite Consultant

Managing the whole project from the first to end. The project is broken into module / phases and each modules will contain the each project plan to archive the target. I was very enthusiastic to work with the challenges. 

Managing and handling wide range of customers who are into many sectors without any hurdle and balancing their satisfaction. It was really fascinating and challenging work but this was smoothly handled by myself and my team.Archiving each milestone ends positively. This gives us the good strength to start the new targets.

Working with customer to identify and define the scope of the project.
Coordinate project schedules, resources, timelines and information 
Check Coordinates project activities and ensures all project phases are documented appropriately 
 Work on Risk Analysis and the mitigation plan
 Monitor project progress and handle any issues that arise 
Create and maintain comprehensive project documentation, plans and reports 
Present solutions and recommendations in written or oral reports to key decision makers. 
Prepare documentation and present progress reports to customers 
Identify issues, create hypotheses and execute analysis; Translate data into meaningful insights. Ability to understand and design functionalities 
Analyze IT requirements within companies and giving independent and objective advice on the use of IT
Liaise with staff at all levels of a client organization
Assume responsibility for project tasks and ensure they are completed in a timely fashion

Project Leader

Developed  Reporting and Custom Application with latest technologies. Using MySQL , MSSQL and for database tools. Starting from Planning to Testing , Following SDLC (Software Development Life Cycle ) methods to complete the project..

•	Initiated the GreenHR a cloud based SaaS HCM.
•	Developed Complete GreenHR product.

Programming & Implementation Consultant

I involved to develop .NET Application , PHP Websites and Applications, Converting the mobile prototype to a native mobile application. It was a really great experience when working with ITSthe1 Solution. There are a lot of ways to learn and execute to our career.

Software Developer

Certified Oracle NetSuite & AI Consultant

English

Sinhalese

Tamil

Kempinski Customer Portal is a web application which made easy for customers to communicate via Kempinski Customer portal. Which can handle more than 200 Owners and contain modules such as in built email system, Request Management , Financial Documents , Bulk Messages etc.

Kempinski Customer Portal

EPRE is a Real Estate Company Web Application which manage property and its make EPRE Users to manage their property easily.

EPRE Web Application

The application run in SSRS and the parameters are passing through ASP.NET page and the drop downs are filling with AJAX request . 

Reporting Application

This is a bridge which all the device go across this path to make payments to Kodiaksnow Company

KodiakSnow Paypal Payment Bridge

This is a custom CMS  and E-Commerce Website to update content , Product details and upload photos to website  . Paypal payment method available in this website.

StripWhites

This application allow Facebook users to search friends using their image. The technology used in this application is Face Reorganization . Using uploaded image searching the matching image and displaying for this i used Facebook API to get data from Facebook


Facebook Friend Seek Appliction

This is a custom CMS to update content and upload photos to CMS. Some additional functions like gallery sorting using jQuery used in this project.

Sunbird

Tropical Homes

NetSuite ERP Implementation for CofeApp

One of the simplest Human Resource Management System built with cutting edge technologies.  It helps the  employees to do their work easily with collaboratively. This has dramatically reduced the HR Administrators time and help them to think strategically  for the organization. 

My role in this project is, project leader, I started building the simplest but more technical product from the scratch to end. 

GreenHR

The Website gives an elegant look the website. and with Multiple languages. 

Emerald Palace -  Kempinski Hotel

We made a huge modification on the existing code, Using many latest technologies and avoiding classical way of web development

EPG Hotel & Resorts

KodiakSnow is a Canadian company. The Android application allow KodiakSnow Customers to make their payments through the android device and can see the tractors available position. And they can request KodiakSnow to send tractors to users address.

KodiakSnow Android Application

Your NetSuite limits might not be real.

I see companies hitting walls with their system every week. They assume they've outgrown the platform or need a third-party app to fix it.

But usually, the wall is just a permission problem disguised as a platform problem.

I remember watching an accounts payable clerk spend 30 minutes every morning manually copying vendor payment data into Excel. She was reformatting it by hand to send to the bank.

When I asked why, she said NetSuite couldn't handle their bank's specific format.

We looked at the native payment file export feature together. It took two clicks to generate exactly what she needed. She stared at me for a second and realized she had been doing six months of manual work for nothing.

The companies getting 80% value from their ERP aren't smarter. They don't have better technical teams.

They just refuse to accept "that's how the system works" as an answer.

They treat NetSuite as a business process tool, not just accounting software. They involve operations, sales, and warehouse teams so the system reflects how work actually gets done.

If you find yourself exporting data to Excel to finish a task, that is your signal.

The capability is likely already there. You just haven't unlocked it yet.

No alternative text description for this image

Everyone's building AI agents wrong.

McKinsey recently released data showing fewer than 10% of companies have scaled autonomous AI agents.

Meanwhile OpenAI reports that 20% of enterprise usage happens through simple tools like custom GPTs.

I'm starting to see a pattern emerging from the noise.

The market has stopped waiting for full autonomy.
It voted for human supervision instead.

We spent the last year obsessed with the idea of AI replacing us... ignoring the reality of AI multiplying us.

The friction is rarely in the model performance anymore.
The models are converging. They are all "good enough."

The real gap is in the workflow architecture.

Autonomy fails because models lack the context that lives in your head. They hit a wall when they need specific organizational nuance (the "fact gap").

Workflows succeed because they keep the human in the loop for judgment. They offload the heavy lifting but keep the steering wheel in your hands.

> A pharmaceutical company reduced clinical study prep by 60% using this exact approach.
> They didn't ask an agent to "figure it out."
> They built a specific workflow where AI analyzes data and a human validates it.

Stop trying to build a digital employee that works while you sleep.

Start building the integration layer that makes you better while you work.

Technology serves human capability expansion.
Not replacement.

What do you think? Are you seeing more value in agents or workflows?

Like & Share if you prefer control over hype ♻️

#AIWorkflows #HumanInTheLoop #AIAgents #EnterpriseAI #AIImplementation

The AI models you chase may not matter.

We treat ChatGPT, Claude, and Gemini like sports teams.

We cheer for the updates. We compare the leaderboards. We think the secret to winning is picking the right jersey.

I used to spend hours testing prompts across five different windows to see which one was slightly smarter.

I thought I was being rigorous. I realized I was actually wasting time.

The gap between these models is shrinking to nothing.

They are all converging. Intelligence is becoming a commodity.

The companies winning right now aren't the ones with the "best" model.

They are the ones who stopped shopping and started building.

The real gap isn't intelligence. It is context.

Models know everything about the world but nothing about your business.

They don't know your quarterly goals. They don't know your brand guidelines. They don't know why your last project failed.

A slightly smarter model doesn't fix a broken workflow. It just generates the wrong answer faster.

I'm seeing a clear pattern with the clients I work with.

The ones who succeed don't ask "which model is best?"

They ask "how do we feed our context into any model?"

-> They map their workflows first
-> They build integration layers
-> They treat the AI as an engine, not the whole car

Stop waiting for a smarter model to save you.

The competitive advantage is hiding in your boring, unmapped processes.

It is going to be hard work to map it all out.

But that is where the value lives.

What do you think?

Like & Share if you are done with the hype train 🚂

a679493205ab5a6f6a91134c5f3f0399.pdf

AI is writing its own upgrades.

I used to think the biggest AI risks were obvious, but I've learned many critical dangers are hiding in plain sight, often overlooked. There's a subtle pattern emerging in AI's rapid growth that demands a different kind of attention we aren't yet giving it.

We tend to look at the loud stuff. Robots. Hollywood scenarios.

But Dario Amodei from Anthropic points to a structural shift that is actually happening right now.

He calls it a "country of geniuses in a datacenter." 🧠

Imagine 50 million geniuses.
Working 100x faster than humans.
Available instantly.

That sounds great for productivity.

But here is where the math breaks:
These systems are starting to write their own code.

-> Current AI writes code
-> That code builds better AI
-> That better AI writes even better code

This is a recursive loop. 🔄

We are used to linear time. We implement systems based on static capacity. But this capacity expands faster than we can validate it.

Traditional safety checklists fail here. You can't write enough rules for a system that evolves this fast.

The fix requires better architecture.

Amodei suggests "Constitutional AI."

We have to teach the models principles, not just commands. We have to instill values deep in the training layer so the system aligns itself, even when it outpaces our ability to monitor it.

It creates a system that wants to be safe, rather than one forced to be safe.

This is the only way to survive the speed of recursion.

We need to stop optimizing for speed and start optimizing for architectural integrity.

What do you think? Does teaching AI "values" sound safer than hard rules?

Like & Share if you agree we need a new approach ♻️


#AIAlignment #Anthropic #SystemArchitecture #TechStrategy #FutureOfWork #AIrisks #SabranHameed

You spent how much on NetSuite? And your team is still reconciling data in Excel. I see this pattern everywhere. Companies talk about their NetSuite i

Why Your NetSuite Investment Isn't Working

Nobody told you what you actually bought.

I walk into projects where the CFO is frustrated and the controller is exhausted. They can explain exactly what reports they need. They know precisely which workflows are broken.

But nobody can tell me what they asked for during the original implementation.

There is a gap between "what we wanted" and "what we communicated" that costs companies years of productivity.

I saw this recently with a revenue recognition project.

The CFO wanted to see deferred revenue broken down by product line and customer segment in real time. That was the business need.

But the technical request that went to the implementation partner was just "configure deferred revenue."

So the partner built a rigid chart of accounts that tracked revenue only at the highest level. They delivered exactly what was asked for technically. And it was completely useless operationally.

We ended up having to bolt on a separate reporting tool just to get the data the CFO thought he had already bought.

The vendor didn't fail them. The software didn't fail them.

The translation layer never existed.

I used to think implementation was about configuring software correctly. I thought if you knew the features, you could solve the problem.

Now I realize the real work happens before you touch the keyboard.

It is about asking "what does success look like for the end user" instead of "what are the technical requirements."

If you don't build that translation bridge first, you aren't implementing a system.

You are just configuring a very expensive disappointment.

Stop buying tools. Start building systems.

We used to measure innovation by how many new tools we could procure. We assumed that if a problem existed, a purchase order would solve it.

The data now tells a different story.

Knowledge workers are juggling nearly double the applications they used just a few years ago. We are losing almost an hour every week not to work, but to the friction of switching between the tools meant to help us work. That is forty-four hours of pure waste per employee annually.

We need to change how we evaluate technology investment.

My mental model for this has shifted from acquisition to consolidation. I no longer look for the tool that adds a new capability. I look for the architecture that removes an existing barrier.

When I audit a tech stack, I ask specific questions. Does this addition integrate or isolate? Does it require a bridge we haven't built yet? Does the cost of fragmentation outweigh the benefit of specialization?

We often see CFOs viewing software simply as a line item expense. But the real cost isn't the license fee. It's the operational drag caused by a patchwork environment where data lives in silos and workflows break down at the seams.

ROI doesn't come from buying more capacity. It comes from integrating the capacity you already have.

The most effective leaders are moving toward centralized platforms. They are rolling out technology in stages to manage the cognitive load on their teams. They understand that a consolidated system offers visibility that a fragmented one never can.

Stop adding noise. Start building coherence.


#StopBuyingTools #BuildSystems #TechStackConsolidation #WorkplaceEfficiency #DigitalTransformation

Why spend $15K when NetSuite features you already own can do the job?

Most organizations I walk into are paying double for problems they've already solved.

They have the full suite.

They use about 30% of it.

Then they go shopping for third-party apps to fix gaps that don't actually exist.

I recently watched an accounts payable clerk spend 30 minutes every morning manually copying payment data into Excel to format it for the bank.

She had been doing this for six months.

We enabled the native payment file export feature.

It took two clicks.

Her 30-minute daily headache became a two-minute task.

The gap wasn't capability.

The gap was knowing what they owned.

I see finance teams buying inventory tools for $15,000 a year when NetSuite Advanced Inventory is sitting right there in their subscription, dormant.

I see revenue teams bolting on reporting software because the implementation partner built a rigid chart of accounts instead of asking what the CFO actually needed to see.

This isn't usually a software problem.

It is an awareness problem.

You don't need another tool.

You need to integrate the one you already paid for.

Helping companies close that gap is what I do.

If your team is exporting to Excel just to do their job, we should probably talk.



#NetSuite 
#ERP 
#FinanceAutomation 
#SoftwareOptimization 
#BusinessEfficiency

Your calendar is worth more than GPT-5.

By 2026, I predict the most valuable AI company won't be the one with the smartest model, but the one deeply embedded in your calendar.

The recent ServiceNow deal with OpenAI isn't about features. It is a land grab for context.

Microsoft, Google, and Salesforce are racing to own your internal workflows because context creates lock-in.

If an AI knows your quarterly goals, reads your emails, and understands your brand voice, switching platforms becomes impossible.

We are moving from a battle of intelligence to a battle of integration.

The winners will own the plumbing of your daily operations, not just the chat window.

You need to stop asking which model is smarter and start asking which ecosystem you are willing to marry for the next decade.

Because once they have your context, they have you.



#AIIntegration #ContextIsKing #EnterpriseAI #TechEcosystems #AILockIn

OpenAI just admitted they broke GPT-5.2 on purpose.

Sam Altman recently admitted OpenAI deprioritized writing quality in GPT-5.2 to focus on reasoning and coding.

This isn't a failure. It is actually a perfect example of reality.

I see companies try to ignore this dynamic every day.

You buy a massive enterprise suite and expect it to be both infinitely customizable and instantly usable out of the box.

You push for rapid feature deployment and are surprised when system stability degrades.

You want deep analytical complexity but demand a simple, intuitive user interface for junior staff.

There is always a cost.

When you refuse to choose what suffers, the system chooses for you.

Usually, the thing that suffers is the user experience or the integration quality.

The difference between a strategic leader and a reactive one is simple.

Reactive leaders find out about tradeoffs when their support tickets spike.

Strategic leaders decide where the friction lives before writing a single line of code.

You can have speed. You can have depth. You can have simplicity.

But you cannot optimize everything at once.

Pick your poison before the market picks it for you.

What do you think?

79aa59259ca56964427fed69d44dbef2.pdf

Non-technical people are easily building applications and websites.

I'm starting to notice something that feels somewhat overlooked.

Pure technical skill doesn't carry the weight it used to.

OpenAI found that 75% of users complete tasks they couldn't do before AI. Not faster. Different entirely.

Salespeople write their own scripts now. Marketers build internal tools. Operations managers automate spreadsheets without calling IT.

They aren't learning to code. They're mixing what they already know about their work with enough AI literacy to move forward.

I used to think technical gatekeepers would stay ahead because they understood the systems.

But domain experts are moving faster because they understand the problems.

You don't need to know how the engine works if you know where you're going.

The people moving forward right now? They understand their work well enough to ask AI better questions.

Technical polish comes after you solve the right problem.

What I'm seeing: if you know the business context, you have what you need to build solutions.

Does this match what you're seeing? Leave your favourite AI app builder in the comments.  

#AILiteracy #NoCode #DomainExpertise #AITransformation #FutureOfWork

The NetSuite feature existed. For six months.

I watched a client spend six months vetting vendors to find the perfect platform.

A year later, their AP clerk was still manually copying data into Excel for 30 minutes every morning.

The system could do it in two clicks.

The clerk didn't know because the implementation team never asked how the payments actually happened.

I used to believe selection was the critical phase.

I see now that the tool is rarely the bottleneck.

The friction lives in the translation layer.

A suboptimal system works with great integration architecture.

A perfect system fails if it simply mirrors your existing chaos.

The priority is translating the business reality into the configuration.

What do you think?



#NetSuite #SystemImplementation #BusinessProcess #DigitalTransformation #ChangeManagement

Selection committees waste months on nothing.

I've been losing sleep over this one lately.

We spend months picking the right enterprise system. Committees form. Feature comparisons get built. The whole selection process feels like the hard part.

Then we spend years building workarounds for what we just bought.

I'm starting to notice a pattern. The selection process might be the decision that matters least.

Here's what I think we're missing.

We buy systems to fix our chaos. We expect the software to organize us. But software doesn't organize anything on its own.

Software amplifies what you feed it. You feed it fragmented processes, you get faster fragmentation.

The friction isn't in the tool. It's in the translation layer between your reality and the system's structure.

You're buying potential. But someone needs to translate your operational mess into configuration logic. Someone needs to know both worlds.

I'm seeing a lot of organizations skip this entirely.

They bring in vendors who know the tool but don't understand the business. Or they hand it to internal teams who know the context but don't see the technical limits.

You end up with a shiny platform. And the same manual processes running underneath.

The tool works fine. The translation layer is what's missing.

If you're stuck in this loop, you might be asking the wrong question. It's less about which system to buy. It's more about who's going to make the system fit your world.

What do you think? Do you have someone playing that bridge role, or does it feel like everyone's just working around the software?

#EnterpriseSystem #SoftwareImplementation #DigitalTransformation #BusinessProcesses #SystemIntegration

SuiteScript isn't dying. Your old role is.

Is SuiteScript truly becoming obsolete?

I honestly don't think so.

For a long time, the job was mostly syntax. We spent hours memorizing API calls and object structures, acting as human translators between business logic and the terminal.

Now, tools like Claude handle that translation almost instantly.

But here is where I think people get confused.

The bottleneck didn't disappear. It just moved upstream.

If you ask an agent to build a solution but you don't actually understand the record lifecycle or the governance limits... you're just going to create a structural mess at record speed.

The machine can write the function. But it can't feel the friction in the workflow.

-> You still have to define the trigger point.
-> You still need to map how data moves between systems.
-> You have to catch the logic errors that look syntactically perfect.

We are shifting from bricklayers to architects.

Claude is just a really fast trowel. You still have to know how to read the blueprint.

I suspect the value of "pure coding" drops, while the value of "system integration" is about to skyrocket.

What do you think?

Like & Share if you're ready to be an architect. ♻️



#SuiteScript #NetSuite #SystemIntegration #DeveloperEvolution #AIandCoding

taplio

The Battle

Lazar Jovanovic

Sabran Hameed

Followers

Posts

Engagements

Likes

Performance ScoreLazar Jovanovic's LinkedIn Performance

Performance ScoreSabran Hameed's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Lazar Jovanovic

Sabran Hameed

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);}Lazar Jovanovic's LinkedIn Performance

Performance ScoreSabran Hameed's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreLazar Jovanovic's LinkedIn Performance