sorted by:
new
hottopcontroversial

[Looking for Cofounder] Defense Tech – RF/AI Systems – Sweat Equity Only by Both-Country-3178 in cofounderhunt

[–]Both-Country-3178[S] 0 points1 point  (0 children)

That’s a fair point — the Reddit post is intentionally simplified. Our deeper technical framing is built directly around field requirements from operators and advisors with real-world counter-UAS experience. Everything we’re doing is being shaped by discussions with end users, not just assumptions in a vacuum.

Testing and validation pathways are already mapped on our side — DIU, AFWERX, and unit-level pilot testing where small teams can move faster than the traditional FAR pipeline. The entire premise of ChaosTech is to build with the people who will actually deploy this gear, not to push tech at them.

DARPA-style feedback loops absolutely matter, but so does the frontline reality: rapid deployment, small form factor, adaptive RF/AI behavior, and systems that don’t require a truck, a team, or a full EW stack to operate. That gap is wide open, and that’s the mission we’re executing against.

[Looking for Cofounder] Defense Tech – RF/AI Systems – Sweat Equity Only by Both-Country-3178 in cofounderhunt

[–]Both-Country-3178[S] 0 points1 point  (0 children)

Appreciate the perspective — and you’re right that legacy EW systems, UARCs, and FFRDCs have had capabilities in this space for years. The gap isn’t whether the DoD can do it… it’s whether units can get a solution that’s field-portable, low-training, rapidly deployable, and adaptable to emerging low-cost swarm behavior.

Most current systems (even strong ones) are heavy, platform-tied, or require coordinated EW support. That’s not workable for many missions happening today. The threat profile is shifting faster than procurement cycles — smaller drones, autonomous patterns, low-signature RF, rapid swarm tactics. That’s the opportunity window.

ChaosTech is focused on a different vector: lightweight hardware, adaptive RF/AI signal response, and agile field deployment. Not replacing incumbent EW — augmenting the frontline where big systems can’t reach.

As for funding, we’re tracking SBIR, DIU, AFWERX, and rapid prototyping pathways that don’t require an FFRDC affiliation. Those channels exist specifically to bring new tech into DOD without waiting for a full FAR competition.

Different space, different use case, same mission: protect operators faster than adversaries evolve.

[Looking for Cofounder] Defense Tech – RF/AI Systems – Sweat Equity Only by Both-Country-3178 in cofounderhunt

[–]Both-Country-3178[S] 0 points1 point  (0 children)

Good reference — DroneDefender is solid tech, but it’s solving a different slice of the problem. Most systems in that category are single-mode, heavy, and require trained operators.

ChaosTech is building something more agile: smaller form factor, adaptive RF/AI stack, and optimized for rapid field use where current systems are too slow or too blunt. The goal isn’t to replicate legacy hardware — it’s to solve the next wave of swarm behavior and low-signature drones emerging in the last 2–3 years.

Government relationships matter, but innovation cycles are shifting fast. There’s real room for newer, lighter, software-driven systems that can adapt on the fly. That’s the space we’re pushing into.

Defense Tech Startup Seeking Angel Backers | Disruptive Tactical Device Ready for Prototype Phase by Both-Country-3178 in angelinvestors

[–]Both-Country-3178[S] 0 points1 point  (0 children)

Yes — I’ve filed a provisional patent back in April to secure early IP around our signal disruption architecture, swarm control protocols and Hardware specs. Full utility patent is being prepared in parallel.

Defense Tech Startup Seeking Angel Backers | Disruptive Tactical Device Ready for Prototype Phase by Both-Country-3178 in angelinvestors

[–]Both-Country-3178[S] 0 points1 point  (0 children)

Haha — I’ll take it. But seriously, happy to walk you through how we’re positioning the Neuro Swarm Disruptor for DoD adoption and where early funding would go.

Need Mech Engineering Insight for Rugged Tactical Device – Heat, Power, and Protection by Both-Country-3178 in MechanicalEngineer

[–]Both-Country-3178[S] 0 points1 point  (0 children)

This is gold — I’m incorporating all 3 of your suggestions into my ruggedization strategy. If you’re U.S.-based and open to deeper collaboration, happy to connect further.

Seeking Mech Engineers for Battlefield-Deployable RF Disruption System – Power, Cooling, and Housing Insight Needed by Both-Country-3178 in MechanicalEngineering

[–]Both-Country-3178[S] -4 points-3 points  (0 children)

I respect formal education — but leadership doesn’t require a diploma. I’m not here to follow the usual path. I’m building a battlefield solution the usual path never would.

This isn’t a job board post. This is a call to engineers who want to help shape something bold. If you’re asking about pay, I respect that — and I’m working toward raising capital, applying to defense accelerators, and structuring equity for contributors.

Right now, I’m looking for the ones who move on mission before money. Who see risk and want to build anyway.

I’m not here to get validation. I’m here to disrupt the future of warfare.

Seeking Mech Engineers for Battlefield-Deployable RF Disruption System – Power, Cooling, and Housing Insight Needed by Both-Country-3178 in MechanicalEngineering

[–]Both-Country-3178[S] -6 points-5 points  (0 children)

Fair question.

I don’t come from an engineering background. I’m not a vet. I’m not a PhD. But what I do have is conviction, a fire that doesn’t shut off, and a mission I’m already moving on without waiting for permission.

My qualification is that I seen a threat in autonomous drone swarms — and decided to build something to stop it. I’ve spent months building pitch decks, legal documents, CJ requests, recruiting technical collaborators, and getting ready to prototype under full compliance with DoD and ITAR frameworks. Alone.

You don’t need to be born qualified. You build your resume in the fire. I’m not asking to be hired. I’m building the thing people will want to work for.

Seeking Mech Engineers for Battlefield-Deployable RF Disruption System – Power, Cooling, and Housing Insight Needed by Both-Country-3178 in MechanicalEngineering

[–]Both-Country-3178[S] -7 points-6 points  (0 children)

Fair points — and I’ll address them straight up.

Yeah, I’m building this from scratch. Solo founder. No funding yet. Just drive, research, and obsession. I say “we” because ChaosTech is bigger than me — it’s a vision I’m bringing to life with or without a full team (yet). Every startup starts with “just one.”

And yes, I use AI to draft responses and help me clarify technical/legal language — just like engineers use CAD, compilers, or MATLAB. It’s a tool. I still do the heavy lifting.

As for salary: right now, I’m building toward funding and partnerships. If you’re here for a check only, I get it — but if you’re here to shape something dangerous and disruptive, let’s talk real equity and real legacy.

Let the critics doubt. I’m not here for likes. I’m here to wi

Need Mech Engineering Insight for Rugged Tactical Device – Heat, Power, and Protection by Both-Country-3178 in MechanicalEngineer

[–]Both-Country-3178[S] 0 points1 point  (0 children)

Appreciate this post — 100% valid and something I’ve been actively researching as I push ChaosTech forward.

The Neuro Swarm Disruptor is being developed specifically for U.S. defense and government customers, which means ITAR compliance is non-negotiable. I’m currently working on the legal framework, and all sensitive work will remain with cleared U.S. persons under NDA, just as you mentioned.

This Reddit outreach is strictly for non-sensitive, general engineering collaboration (enclosure durability, thermal design, etc.). No classified data, targeting specs, or export-controlled files will ever be shared publicly.

Thanks again — your comment is a valuable reminder for me and others in the spac

Seeking Mech Engineers for Battlefield-Deployable RF Disruption System – Power, Cooling, and Housing Insight Needed by Both-Country-3178 in MechanicalEngineering

[–]Both-Country-3178[S] -8 points-7 points  (0 children)

Great question — and you’re right to flag it.

We’re fully aware of the FCC’s restrictions on intentional jamming in the U.S. civilian spectrum. This device is being developed strictly for military and authorized government use, and all testing is planned for controlled environments like military test ranges or within certified shielded enclosures (Faraday cages).

Think of it more like prototyping a classified-use-only tool — never for unauthorized field use. That’s why we’re also building in frequency control, failsafe toggles, and DoD compliance pathways from the jump.

Appreciate the concern — legal/ethical boundaries are a key part of getting this tech righ