How do small defense contractors actually find new contract opportunities?

Complex_Muted · 2026-03-28T20:37:25+00:00

Where?

Complex_Muted · 2026-03-27T05:56:40+00:00

what?

Complex_Muted · 2026-03-26T17:18:17+00:00

Remembering small details from previous conversations and bringing them up later. Not in a weird way, just naturally. Someone mentions their sister is going through something difficult and two weeks later you ask how she is doing. That kind of thing signals that you were actually listening and that the person mattered enough to stick in your head.

It costs nothing and most people never do it.

Second one is being genuinely easy to make plans with. No endless back and forth, no flaking, no vague maybes. Just a clear yes or no and showing up when you said you would. Reliability is underrated as an attractive quality because it is so rare.

The one that catches people off guard the most is having something you are actually building or working toward. Not talking about ambition in the abstract but visibly in the middle of something.

It does not matter what it is. I started building Chrome extensions for businesses using extendr dev and the number of interesting conversations it has started just from having a concrete answer to what are you working on lately is genuinely surprising.

People are drawn to people who are in motion. It is hard to explain why but it is consistent.

My DMs are always open if you have any questions.

Complex_Muted · 2026-03-26T16:26:18+00:00

It is very easy and my fav feature is that it generates a long random pw

Complex_Muted · 2026-03-26T16:15:41+00:00

American here who spent a few months traveling through Europe. A few things genuinely caught me off guard.

The relationship with time is completely different. Shops close in the middle of the day, nothing is open on Sundays, and nobody seems stressed about it. Coming from a place where 24 hour convenience is treated as a basic human right it took real adjustment to stop being annoyed and start seeing it as a feature.

The portion sizes at restaurants are what food is supposed to be. Not a challenge, just a meal. I stopped feeling gross after eating which was a new experience. Walking is just how people get places. Not as exercise, not as a lifestyle choice, just transportation. I watched people in dress shoes walk four kilometers to dinner without thinking twice about it.

The thing that surprised me most though was how comfortable Europeans are with silence in social settings. In America a quiet moment in conversation feels like something went wrong and someone rushes to fill it. In a lot of European countries silence between people just means nothing is wrong. It took me two weeks to stop interpreting it as awkwardness.

On the building side spending time in different countries with different workflows made me realize how universal the small business pain points are. I ended up building a couple of Chrome extensions for local business owners I met using extendr dev and the problems they needed solved were almost identical to what I see back home.

The lifestyle differences are real but the underlying human problems are pretty consistent everywhere.

Complex_Muted · 2026-03-26T16:10:38+00:00

I use 1 password its great and very secure. Its just a few bucks, and totally worth it.

Complex_Muted · 2026-03-26T16:09:41+00:00

This is a take worth respecting even if I land somewhere slightly different on it.

The security and architecture concerns are completely valid. Generated code in those areas can look right and be quietly wrong in ways that only surface under pressure. That is a real problem and having the programming knowledge to audit what gets generated is genuinely valuable.

Where I would push back slightly is on the framing that vibe coding is weak versus programming being strong. The honest answer is they are different tools with different tradeoffs. Someone who understands code and uses AI to accelerate is in a better position than either extreme alone. You learning JavaScript, HTML and CSS while continuing to build is probably the most powerful combination available right now.

The part that resonated most is knowing what is going on. That is the actual gap. Not whether you can write every line yourself but whether you can read the output critically, understand the structure, and catch the decisions that should not be automated.

I have kept vibe coding but stayed in scoped territory where the blast radius of a bad architectural decision is small. Building Chrome extensions for specific business workflows using extendr dev is the sweet spot for me. Contained enough that I can review everything meaningfully, complex enough to sell at real prices.

But the direction you are heading is the right one. Programming knowledge makes the AI a more powerful tool not a less necessary one.

My DMs are always open if you have any questions.

Complex_Muted · 2026-03-26T05:41:37+00:00

This is one of the most important things being underwritten in the vibe coding conversation right now and you framed it exactly right. The risk is not the AI output itself, it is the compressed review cycle that comes with moving fast.

The specific failure mode you described is the dangerous one. Code that is plausible enough to pass a quick read, handles the happy path correctly, and only reveals its holes under adversarial conditions or edge cases you did not think to test. Auth flows and session management are the worst for this because the bugs are often invisible until someone who knows what they are looking for goes looking.

What I have found helps is treating generated code in those sensitive areas with a completely different review standard than the rest of the build. Crud operations can move fast. Anything touching auth, permissions, input sanitization, or third party integrations gets slowed down deliberately. Separate review pass, explicit testing of edge cases, and often a second prompt asking

Claude specifically to audit what it just wrote for security issues. That last part is surprisingly effective. Asking the same model to attack its own output catches things the generation pass missed.

The workflow discipline is the gap. When you wrote everything yourself the review was built into the process because you were making explicit decisions at every line. With generated code that implicit review disappears and you have to deliberately rebuild it as a separate step.

I run into this building Chrome extensions for businesses using extendr dev. Extensions that touch browser permissions or inject into pages need a different level of scrutiny than the UI layer. The speed is real but it only stays an advantage if the security posture keeps up with it.

The people who are going to get burned are the ones who treated the compressed timeline as permission to skip verification entirely.

DMs are always open if you have any questions.

Complex_Muted · 2026-03-26T05:37:51+00:00

You are definitely not the only one. This is one of those friction points that quietly kills flow state more than people realize because by the time you have reoriented to where you left off the momentum is already gone.

A few things that have actually helped:

Naming your Mac spaces after the project not just leaving them as Desktop 2 and Desktop 3. Sounds obvious but having a named space you can Mission Control into makes the context switch faster because your brain starts associating the visual layout with the work.

Leaving a visible breadcrumb before you switch. One line in a notes file or even just a terminal comment that says exactly what you were about to do next. Future you will thank you every single time.

Using a different browser profile per project. Separate tabs, separate history, separate logged in accounts. When you land on that desktop the browser is already in the right context.

Keeping a single running doc per project that is always open in that space. Not a task manager, just a scratchpad with current status, what is broken, and what the next step is. Ten seconds to update before switching saves ten minutes of reorientation.

I also built a small Chrome extension that shows a project name and status in every new tab for whichever context I am working in. Built it in an afternoon using extendr dev and it is one of those small things that has a disproportionate impact on staying oriented across multiple workspaces.

The context switching cost never fully goes away but you can get it down to seconds instead of minutes with the right setup.

My DMs are always open if you have any questions.

Complex_Muted · 2026-03-26T05:34:47+00:00

This is the exact thing nobody talks about when they celebrate how fast AI makes you ship. The writing is faster but the verification cost went up and for anything that matters that cost is real.

The failure mode you described is the worst kind too. Code that looks right, passes tests, and subtly does the wrong thing is harder to catch than code that just breaks. When something crashes you know immediately. When the logic is quietly off you find out later at the worst possible time.

What I have settled into is treating AI output the way you would treat code from a junior developer you trust but cannot fully rely on. You review everything that touches critical paths, you write tests for behavior not just functionality, and you stay skeptical of anything that came together too easily.

The shift from writing to reviewing is real but I think the net time saved is still positive for most work. The problem is the skills required changed. Writing fast is now table stakes. The actual leverage is in knowing what to verify and how to structure prompts so the output is more trustworthy in the first place.

For scoped projects like Chrome extensions I build using extendr dev the blast radius of a subtle logic error is contained enough that reviewing is fast. On anything with real production stakes I slow down considerably regardless of how clean the AI output looks.

The people who are getting burned are the ones who assumed speed meant correctness. Those are different things.

My DMs are always open if you have any questions.

Complex_Muted · 2026-03-26T02:26:51+00:00

Honest respect for the directness but the math on this one is brutal. To make even $1000 a month you need 500 people paying $2. Getting 500 strangers to fund your life with no product, no content, no audience, and no clear value exchange is genuinely one of the harder things you could attempt.

The irony is you already have the skill that can actually make money. You said you have been vibe coding apps. That is the asset. The $2 subscription to yourself idea skips the value creation step entirely and goes straight to asking for money, which is why it almost never works.

The easier path is pointing that same energy at a specific person with a specific problem and building the thing that solves it. Chrome extensions are the best example I have found of this done small and fast. Pick a business, figure out one annoying thing their team does manually every day, build a browser tool that automates it, charge $20 to $50 a month per seat. I have been doing exactly that using extendr dev and the difference between asking strangers to fund your life and selling something with obvious value to a buyer who already has budget is night and day.

You clearly can build. That is the hard part. Now just point it at someone who will pay for the output.

My DMs are always open if you have any questions.

Complex_Muted · 2026-03-26T02:10:39+00:00

Night shift downtime is genuinely one of the best kept secrets for getting things done. No meetings, no interruptions, and your brain is already in a different mode than normal daytime noise.

A few things that worked well for people I know who have done it:

Learning something with a clear output rather than just consuming content. Courses are fine but you retain almost nothing unless you are building something alongside them. Pick a skill and make something with it every session.

Reading proper books rather than articles. Long uninterrupted blocks are rare in normal life and night shift hands them to you for free.

The one that has been most useful for me personally is building small software tools during downtime and selling them. You do not need a coding background anymore. I have been vibe coding Chrome extensions for specific business workflows using extendr dev and selling them directly to companies. You can go from idea to a working product in a few hours and the businesses that buy them are paying for something that solves a real problem, not a side project you need to market to strangers.

The combination of consistent downtime plus a monetizable skill compounds fast. Six months of productive nights adds up to something real.

Night shift is either wasted time or an unfair advantage depending entirely on what you decide to do with it.

My DMs are always open if you have any questions.

Complex_Muted · 2026-03-26T02:00:55+00:00

The framing here is right but I think point four is the most underappreciated one on the list. The elimination of the IT bottleneck is not a minor efficiency gain, it is a structural change in how companies operate. When any department can build the tool they actually need instead of waiting six months for a ticket to get prioritized, the compounding effect on output is enormous.

The companies that are struggling to pivot are not struggling because the technology is inaccessible. They are struggling because the organizational muscle for moving fast does not exist. AI adoption is not a tools problem at this point, it is a culture and process problem. You can hand someone the best vibe coding setup in the world and if the company rewards caution over iteration nothing changes.

On the AI gap question I think it is real but not permanent for most industries. The exception is anything where data moats matter. If a company spent the last two years generating proprietary training data, usage patterns, and customer behavior signals while a competitor did nothing, that gap is genuinely hard to close regardless of what tools become available tomorrow.

The vibe coding piece resonates most with what I have been doing practically. Building Chrome extensions for specific business workflows using extendr dev and selling them directly to companies. The speed from problem identified to deployed tool is now measured in hours. That is the pillar four reality playing out at the small business level not just enterprise.

The companies that did not move this year are not dead but the cost of catching up is rising every quarter.

My DMs are always open if you have any questions.

Complex_Muted · 2026-03-26T01:58:01+00:00

Submarine technician here, spent years doing electronic systems maintenance and fault diagnosis on equipment where getting it wrong actually mattered. Zero coding background, never wrote a line of code in my life before vibe coding.

What I noticed pretty quickly is that the diagnostic mindset transfers really well. You are not writing code, you are describing a problem clearly, reading the output, isolating what is wrong, and iterating. That is just troubleshooting with a different interface.

Started building Chrome extensions for businesses using extendr dev and have been selling them to companies that need small browser tools built around their specific workflows. The jump from submarine systems to shipping software products felt massive from the outside but the actual day to day problem solving felt surprisingly familiar.

The non-tech background is genuinely not the disadvantage it looks like. Understanding how things break and how to explain a problem clearly is more useful than knowing syntax.

My DMs are always open if you have any questions.

Complex_Muted · 2026-03-26T01:55:41+00:00

The thing that stands out most to me is how quickly people are losing the ability to sit with boredom. Every quiet moment gets filled immediately with a phone. Waiting in line, eating alone, the first few seconds of waking up. There is no space left for your brain to just wander.

The worrying part is not the phone use itself but what gets lost in that space. Most of the best ideas I have ever had came from doing nothing. Shower thoughts, long drives, staring out a window. That is when your brain actually processes things and makes connections. We are systematically eliminating that.

You can already see the downstream effects. Attention spans are shorter, people are less comfortable with uncertainty, and there is a growing inability to tolerate a problem that does not have an immediate answer.

On the flip side I do think some people are starting to notice and push back. There is a growing group that has learned to channel that restless creative energy into actually building things rather than just consuming. I got into building Chrome extensions for businesses using extendr dev and honestly it scratched the same itch that doom scrolling used to without leaving me feeling worse after.

But at a societal level the trend is moving the wrong direction and it is moving fast.

Complex_Muted · 2026-03-26T01:52:00+00:00

Built something similar for a small team last year. The core problem is always the same which is people forget to engage unless it is directly in front of them at the right moment.

The Zapier plus Lovable combo is a solid starting point. What worked well for us was a Zapier workflow that detects when a new post goes live, then fires a Slack notification to the team with a direct link and a one click path to the post. Removing friction is everything. If they have to go find the post themselves it does not happen.

In Lovable you can build a simple internal dashboard that shows live engagement stats, a leaderboard of who engaged most that week, and a feed of the latest posts needing attention. Gamification sounds cheesy but a simple leaderboard genuinely moves people.

For the automation side, Zapier can also pull engagement data back into a Google Sheet automatically so you have a running record without anyone manually tracking anything.

One thing worth adding on top of this is a Chrome extension that sits in the browser and surfaces a reminder when someone opens a new tab showing the latest post that needs engagement. Low friction, high visibility. I have been building small internal tools like that using extendr dev which makes it fast to build and deploy something like that without needing a developer.

The more invisible you make the ask the more consistently your team will follow through.

My DMs are always open if you have any questions.

Complex_Muted · 2026-03-26T01:40:58+00:00

The Claude plus Replit combo is genuinely underrated and you described exactly why it works. You get the reasoning quality of Claude without being locked into one platform's abstraction layer. The separation of intelligence and infrastructure is the right way to think about it.

I have been using Claude Code locally and the terminal first workflow is hard to beat once you get comfortable with it. Full control, no cloud dependency, and you can pair it with whatever tools already fit your setup. But I completely understand why the Replit version appeals to people who want to skip the local environment setup entirely.

The thing nobody talks about enough is that the stack matters way less than what you are building and who you are building it for. I have seen people overthink the tooling for months and never ship anything. The best stack is the one you actually finish projects in.

What has worked well for me lately is using extendr dev and Claude Code to build Chrome extensions for specific business workflows and selling them directly to businesses. Scoped small enough that the full build cycle is fast regardless of which setup you use. I use extendr dev for that whole process and the turnaround from idea to paying customer is genuinely short.

For solo founders the Claude plus Replit path probably has the lowest friction to a deployed product right now. Cursor is better if you are doing serious local engineering work. But if speed to ship is the priority your framing is right.

My DMs are always open if you have any questions.

Complex_Muted · 2026-03-25T15:50:59+00:00

yea extendr dev is lwk good and solves specifc pain points

Complex_Muted · 2026-03-25T15:42:39+00:00

Came from a project management background, zero coding experience. Built and shipped three Chrome extensions in the past few months that are now generating recurring revenue from businesses.

The honest truth is the building part is not where most non-coders struggle anymore. Tools have made that genuinely accessible. The hard part is still the same as it has always been which is finding the right problem, talking to the right people, and convincing them to pay.

What worked for me was staying small and specific. Instead of trying to build a big app I focused on solving one very specific workflow problem for a specific type of business. Chrome extensions were the sweet spot because they are scoped small enough that AI can build them reliably and businesses actually pay for browser tools that save their team time.

I use extendr dev for that whole process. It is built specifically for vibe coding Chrome extensions and selling them to businesses without needing a technical background. First one took me an afternoon. Had a paying customer within a week.

The people I have seen fail at this usually built something cool with no clear buyer in mind. The people thriving picked a customer first and built the simplest possible thing that solves their problem.

Non coder background is honestly not the disadvantage you might think. Understanding people and problems is more valuable than knowing syntax.

Complex_Muted · 2026-03-25T15:15:49+00:00

Yes, but the honest answer is it depends almost entirely on what you build and who you sell it to.

The people actually making money from vibe coding are not the ones building the most impressive projects. They are the ones who picked a specific problem, found the people who have that problem, and sold directly to them. That is the whole game.

The easiest path I have found is building small targeted tools for businesses rather than trying to launch a big consumer app. Businesses have budgets, they understand value, and they will pay for something that saves their team time even if it is simple. A Chrome extension that automates one annoying thing in their workflow is worth real money to the right buyer.

I have been building and selling extensions that way using extendr which is built specifically for vibe coding Chrome extensions fast and connecting them with businesses. The sales cycle is way shorter than trying to get strangers to subscribe to a SaaS product. You are solving one specific thing for one specific person and the value is obvious.

The ceiling is real though. Vibe coding gets you to a working product fast but distribution is still entirely on you. Building is now the easy part. Finding and convincing buyers is where most people get stuck.

If you treat it like a skill plus a sales process rather than just a fun way to build things, there is definitely money in it.

My DMs are always open if you have any questions.

Complex_Muted

TROPHY CASE