r/hwstartups • • 46m ago

Our CNC estimator gives me a price. Would I send it to a customer?

1 Upvotes

I pulled up a CNC drawing from an order we’d already delivered. I knew what we’d charged and what the job had actually cost us. I wanted to see what our estimator would come up with.

It gave me a number. For a minute I was just happy it worked. Then I looked back at the drawing and saw a tight tolerance on one of the holes. I couldn’t tell whether the estimate accounted for the extra machining and inspection that might need. If this had been a live order, I’d have picked up the phone and called the supplier before sending the quote.

I remember closing my laptop and telling Praveen, “I can show someone that it works. I’m still the person who has to decide whether to trust the number.”

That was a hard thing to admit. I’d spent months trying to build the software myself, with some help from interns. Getting an estimate out of a drawing felt like progress. Looking at that same drawing, I could finally see how much work I’d been doing in my head without realising it.

I started Ecostel on my own in 2024. We began as a proprietorship and moved to a private limited company after customers started coming back. Praveen, my old batchmate, joined to run manufacturing operations. I handle sales and spend a lot of my time talking to customers. Today, we have repeat customers for CNC machining and sheet-metal fabrication, and we’re incubated at IIT Madras.

The thing that keeps me going is that we get to see this problem every week. When a customer sends a drawing, they want to know what it’ll cost, when they’ll get it, and whether they need to change anything before we make it. I want to build software that gives them a clear answer and shows our team what still needs an engineer’s judgement.

I’m looking for someone to join our founding team and build that with me. Someone who’s shipped software, likes talking to users, and wants to make both the product and engineering decisions. In the first 90 days, I’d love for us to sit with Praveen while he works through real quotes, test the estimator against past jobs, and get a quoting workflow into his hands that he can actually use on new orders.

We’re running lean, and the initial cash compensation will be modest. I’m happy to share the range in the first conversation. After six months of working together, if we both want to keep building for the long term, I’m open to discussing equity.

f you’d like to build this with us, DM me in 4–6 lines:

  1. What you shipped — One product or feature, who used it, and a link if you can share one.

  2. What you owned — One product or technical decision you made and why.

  3. What happened — One result, piece of user feedback, or thing you changed after launch.

A short description is fine if the work is confidential. LinkedIn or portfolio optional.


r/hwstartups • • 2h ago

I started building an AI-native device with an ESP32 and my gaming PC

0 Upvotes

I started building an AI-native device with an ESP32 and my gaming PC

In my last post, I shared some thoughts on what I think AI-native hardware should be. This time I want to talk about something more hands-on: how I started exploring those ideas with an ESP32, and how it gradually turned into a much more complicated system.

At the beginning, I really just wanted to build a better voice input device for myself.

I work on several projects at the same time and constantly switch between different applications. I've also become pretty used to speaking instead of typing. For me, voice input is genuinely faster, especially when I have a lot of thoughts I want to get out.

But there's an obvious problem. Human thoughts aren't exactly linear.

Sometimes I suddenly remember something else halfway through a sentence. Sometimes I forget a word, or realize what I just said wasn't quite right and start explaining it differently. This happens all the time in normal conversations, but traditional speech-to-text tools tend to turn all of it into text. The result can be a long paragraph full of filler words, repetitions, and ideas that don't quite connect. (Typless solve some of that, but not good enough)

So I started wondering if I could build something that didn't just transcribe my voice, but understood what I was trying to say and helped organize it based on what I was doing.

I also wanted it to gradually learn how I express myself in different situations.

For example, the way I talk to a friend is different from how I discuss a technical issue with a developer or write a GitHub Issue. The underlying idea might be the same, but the way I want to express it isn't.

I'd also like the system to notice when I've left something out. If an explanation is missing an important detail, it could use the available context to help fill it in, or ask me to confirm something, instead of blindly expanding everything I say.

And I don't want to explain the same preferences every time. If I've already corrected similar text many times, the system should gradually pick up on that.

Putting all these ideas together sounds like a pretty complicated project. But once I started working on it, I realized I could break it down and begin with something much simpler.

What I used to get started

I didn't buy any special AI development hardware for this. Most of what I used was stuff I already had.

Hardware:

  1. ESP32 development board ESP32-S3-Touch-AMOLED-1.8 — My original hardware prototype. Xtensa® 32-bit LX7 dual-core processor (up to 240 MHz) 512 KB SRAM, 384 KB ROM, 8 MB PSRAM, and 16 MB Flash. The board I used has a display, a mic, a separate IMU, and touch controls, WIFI + BLE which made it useful for experimenting with different interactions beyond voice input. Got it

  2. MacBook Air (2022) — My main development machine for coding, debugging, and testing the client software.

  3. A regular gaming PC — My personal desktop with an AMD Ryzen 7 7700, AMD Radeon RX 7900 GRE, and 32GB RAM. I use it as a local AI server for speech recognition and LLM inference.

Software, open-source projects, and models:

  1. ASR Engine: transcribe.cpp — The foundation I used for running local speech recognition.

  2. LLM Engine: llama.cpp — For running language models locally.

  3. KnowVoice Harness — A layer I built to connect and manage the different parts of the system, including LLM context, personal memory, text processing, and the overall workflow.

  4. ASR models: Parakeet, Whisper, Qwen3-ASR-0.6B, and SenseVoice Small. These are some of the models I've been exploring and comparing.

  5. LLM models: Mostly smaller models that can run on consumer hardware, including MiniCPM5-2B-GGUF and Qwen3.5-4B-4b Q4_K_M

That's basically the setup.

One thing I really like about building things today is that we no longer have to implement speech recognition or LLM inference from scratch. There are already some excellent open-source projects that we can use and combine.

What interests me more is figuring out how to connect all of them and make the whole system work for the way I actually use it.

Getting the basic system working

The first part was pretty straightforward.

Capture audio on the ESP32, send it to the server, run ASR to transcribe it, pass the text through an LLM to clean it up, and send the result back to the device I'm using.

That's the basic pipeline. For anyone familiar with ESP32, network communication, and model APIs, I don't think this part is particularly difficult. You can get a minimal prototype working with relatively little code.

And once that's running, you already have a simple voice input tool.

But since my ESP32 board also had a display, an IMU, and touch controls, I started wondering why I shouldn't make use of those as well.

For example, I could use the IMU to detect movements, or use the screen and touch controls for simple interactions. That would let me experiment with it as a small wearable device, almost like a basic smartwatch.

Another direction I found interesting was simulate a HID.

I wanted the device to do more than collect information. I wanted it to interact directly with other devices.

If it could emulate input devices such as a keyboard or mouse, then on platforms that support the necessary HID connection, it could send inputs directly to a target device without requiring our application to be installed on that machine.

I think this is quite important.

Once a system can understand speech and user intent, not everything has to end up as text. Sometimes I want to type something. Other times, I might just want to trigger a keyboard shortcut or control another device.

The hardware could become a general-purpose input and interaction point, while the software decides what kind of output makes sense for the current situation.

Of course, getting this to work properly across different operating systems is another problem. HID support, connection methods, and permissions aren't exactly consistent across platforms.

But as a hardware prototyping direction, I find it pretty interesting. I don't think a physical device necessarily needs to be limited to one fixed type of input.

I also wanted the hardware to collect audio outside of active voice input.

For example, during a meeting or technical discussion, it could capture audio with the participants' knowledge and consent, and send that information to the server for processing. Instead of immediately typing the result into an application, that information could become useful context for future interactions.

That's roughly where my early hardware experiments started.

The part that ended up taking much more of my time was the software.

Local inference turned out to be faster than I expected

One thing I worried about initially was whether local models would be fast enough for everyday voice input.

Voice input is a little different from chatting with an AI assistant. I might tolerate waiting a while for a chatbot to respond, but if I have to wait ten or fifteen seconds every time I finish speaking before the text appears, it becomes pretty annoying.

After running some tests on my RX 7900 GRE, I was surprised by how well it performed.

With the model and inference configuration I was using, I measured around 140+ tokens/s for generation and roughly 2,000 tokens/s for prompt prefill.

I set the context window to 30K tokens, and the combined VRAM usage for the model and ASR was around 6–7GB in that configuration.

I thought that was a pretty good result.

For example, if a particular input task only needs about 600~800 tokens of context, then at 2,000 tokens/s, the prefill part would theoretically take about 0.3- 0.4 seconds.

Of course, that doesn't mean the entire voice input process takes half a second. There's still audio transmission, ASR, context retrieval, LLM generation, and finally sending the text back to the client.

But there's something useful about voice input tasks: most of the time, you don't need to generate a huge amount of text. In most of cases, we can complete the task within 2s (Typical: raw audio 43s, using qwen3-asr-0.6b + qwen3.5-4b-4km-mtp , ASR: 529ms, LLM: harness 1656ms)

A few dozen seconds of natural speech usually doesn't translate into that much written content. If we can control how much context the model receives and help it understand the task correctly, I think getting the whole process down to a few seconds is a realistic target.

MTP (Multi-Token Prediction) optimizations is very useful for this case !!!

For this kind of task, we already have the transcribed text, and we want the model to reorganize it using the available context. Lost of text prediction is correct, so overall performance can be improved by approximately 20% to 30%.

But these experiments made me realize that personal AI devices don't necessarily need expensive computing hardware.

My gaming PC is already capable of handling quite a lot of this work, and I can still use it for other things.

This is also one reason why I prefer separating computation from the physical interaction device.

Models change very quickly, while hardware takes much longer to design and manufacture. If all the intelligence is tied to a processor inside the device, you can easily end up with hardware that's still perfectly functional but can no longer run the models you want to use.

If the ESP32 handles input and interaction while a personal computer or another computing device handles the heavier work, updating models and experimenting with different software becomes much easier.

Then I realized that context was actually the harder problem

Sending transcribed speech to an LLM and asking it to clean up the text isn't particularly complicated.

The harder part is getting the system to understand what I'm actually talking about.

For example, imagine I'm discussing a project with a developer and suddenly say:

"Didn't we already fix this issue? Take another look at that earlier change."

For ASR, recognizing that sentence isn't especially difficult.

But for an LLM without any additional information, it's almost meaningless. Which issue am I referring to? What earlier change? Which project are we even discussing?

I could explain all that background again, but then I'm losing much of the efficiency I wanted from the device in the first place.

So I started adding context awareness to the client software.

The software is mainly split into a client and a server. The server handles ASR, LLM inference, and the Harness, while the client is much closer to the actual working environment.

I've mainly been developing clients for Windows, macOS, and Android. The idea is for the client to understand which application I'm currently using and collect relevant context where it has access and permission to do so.

For example, saying the same sentence in a code editor and in a messaging app should probably lead to different context being retrieved.

I also wanted a convenient way to add things I'm reading, such as web pages, documents, or meeting content, to my personal knowledge base.

That way, when I talk about a related issue later, the system doesn't have to start from scratch.

But that immediately creates another problem: how do we decide what information should actually be retrieved?

Just because the model supports a 30K context window doesn't mean I should fill it with everything I have.

That would increase processing time, and a lot of irrelevant information could actually make the model worse at understanding the current task.

So I started experimenting with organizing information from different sources, clustering related topics, generating summaries, and retrieving relevant information based on the current input.

Later I also began exploring knowledge graphs to manage relationships between different pieces of information.

The time-consuming part wasn't really calling the model. It was figuring out how the information should be handled.

Which information is valuable? Which parts were just temporary discussions? When should something be recalled? If we changed a decision later, which version should the system use?

These become pretty annoying problems once you actually start using the system.

I originally thought I was building a voice input device. Somehow, I ended up spending a large amount of time thinking about context management.

Then I started wondering if it could learn from my edits

There was another thing I found interesting.

After each voice input, the LLM generates a cleaned-up version of what I said. But I don't always use that result directly. Sometimes I still edit it manually.

Maybe I remove unnecessary explanations, change the order of a few sentences, or add some technical details.

For a normal voice input tool, that's usually where the process ends.

But I think those edits are actually valuable.

We have the original speech, the ASR transcription, the LLM's processed result, and the final text I decided to use.

If we compare them, we can see exactly what I changed.

For example, when I'm discussing engineering problems, I often remove unnecessary polite phrases or replace vague descriptions with more specific technical requirements.

If the system sees me making these changes repeatedly, it might gradually learn that I prefer more direct and precise language in that context.

Similarly, if I keep correcting certain technical terms, those corrections could become useful references for future transcription and text processing.

And if I accept the generated text without changing anything, that could also be used as a feedback signal.

Of course, I've also realized that it would be a mistake to treat every edit as a permanent preference.

Some edits only apply to one particular message. Some depend on who I'm talking to. And sometimes I'm simply correcting something the model got wrong.

So I've been experimenting with a feedback and learning mechanism on the server side that can organize these changes and distinguish relatively stable preferences from temporary context.

At least initially, I don't think SFT is necessarily the first thing to do.

I'd rather experiment with memory, preference extraction, and context retrieval before jumping into model fine-tuning. It's much easier to test whether the information is actually helping with the next input.

I've also been exploring another type of learning.

I often discuss AI, hardware, and new technical ideas with friends. Sometimes a conversation produces a lot of interesting thoughts, but a few days later, I can barely remember the details.

So I started wondering what would happen if I could capture those discussions, in situations where recording is appropriate and everyone knows about it, then organize and save the useful parts.

I began experimenting with clustering discussion topics, generating summaries, and storing them in a knowledge base.

The next time a related topic comes up, the system could retrieve information from those previous discussions.

For example, maybe we talked about an ESP32 interaction design last week, and this week we're looking at another hardware problem related to it.

If the system can find the earlier discussion, it might be able to connect the two and remind me of ideas we'd already considered.

I don't just want a tool that produces meeting minutes. I want something that helps me actually use information from past conversations.

This also brings up the difference between long-term memory and current context.

Some information represents confirmed facts or decisions. Other information might just be an idea someone mentioned during a discussion.

If the system treats all of these as equally reliable, storing more information could actually make it less useful over time.

So beyond storage and retrieval, I've become interested in how to filter, update, and connect these different pieces of information.

I've done some other experiments too, including knowledge-graph-based information management and audio-related recognition and analysis. There are still plenty of problems I haven't fully solved.

I won't go into all of them here, otherwise this post will get ridiculously long.

Back to why I wanted to build this in the first place

At some point, I realized that what I was building was no longer just a voice input tool.

Initially, I only wanted to turn messy speech into cleaner, more natural text.

Then I wanted it to understand what I was currently doing. After that, I started wondering whether it could use past conversations and my own corrections to improve how it responded next time.

Which brings me back to what I was talking about in my previous post: AI-native hardware.

I still think that simply connecting an LLM to an existing device and adding transcription, summaries, or conversation features is mostly an improvement to the original product.

Those features can be genuinely useful. But I'm more interested in something else:

As I use the device more, can it actually reduce the amount of work I need to do the next time?

For example, something that previously required a long explanation could become understandable from context.

Something I used to correct every time might already be formatted the way I prefer.

Or a discussion I previously had to search for manually could be brought back when it becomes relevant.

If those things work, I think the relationship between a person and their hardware starts to change.

I also think the personal data accumulated through this process could become valuable in a much broader way.

Over time, with proper filtering and organization, we could build up a useful collection of personal language preferences, knowledge, project context, and correction history.

If the data quality is good enough, that could eventually become useful for SFT or other approaches to personalizing models.

I'm particularly interested in the idea of a personal model combined with continuously improving personal data.

Maybe in the future, we won't all need completely different foundation models. We could start with the same underlying model, but the service it provides becomes increasingly different for each person as it learns from their actual usage.

And one of the things I find most exciting is that we don't necessarily need expensive hardware to start exploring this.

When I began, I was just using an ESP32, a MacBook Air, and a gaming PC with a consumer GPU.

We already have so many good open-source models and software projects that it's possible to experiment with ideas that would have been much harder to build not that long ago.

That's why I'm still working on this.

I've also started developing a dedicated product around these ideas, under the name KnowVoice. The ESP32 experiments were an early part of figuring out what the interaction should actually look like.

My plan is to keep improving the hardware and software together, and open-source the relevant work once the workflows are mature enough.

I'd like there to be two ways to use it.

If you don't want to spend your time assembling hardware, configuring models, or debugging software, you should eventually be able to buy a ready-made device and just use it.

But if you're a Maker who enjoys tinkering, I'd love for you to be able to build on what we've done, change things, and create features or interactions that we haven't even thought of.

I think both are equally interesting. And I'd be especially happy if people took the underlying ideas in completely different directions.

My previous post was mostly about why I think AI-native hardware should work differently. This one is more about how I started experimenting with those ideas, and what I discovered along the way.

I'm curious how other Makers would approach this.

If you have an ESP32 lying around, or an old gaming PC that isn't being used much, what kind of AI device would you try to build?

I'm especially interested in hearing from people working on personal memory, context management, or systems that learn from user feedback.

I'll keep sharing more of the technical details and experiments as the project develops. If you're working on something similar, I'd love to compare notes.

We are currently trying to turn this product into a real product named KnowVoice. If you are interested, feel free to reach out at any time.


r/hwstartups • • 9h ago

I've built a working hardware prototype, but how do I know if it's worth turning into a business?

2 Upvotes

I'm an electrical engineering student and software developer, currently taking an entrepreneurship course.

For the past few months, I've been developing a product called PocketOhm, a compact Bluetooth electronics measurement system intended for students, hobbyists, and makers.

What started as a class project has turned into a fairly substantial hardware and software development effort, and I'm now trying to determine whether there's enough commercial potential to justify taking it further.

The product:

  • Bluetooth DMM: DC voltage, resistance, and continuity measurements.

  • Measurement logging: Save physical measurements directly in the mobile app.

  • Interactive circuit design tools: Use saved measurements in voltage divider, Ohm's law, RC filter, and other calculators.

  • Component identification: An experimental expansion module for identifying and measuring electronic components.

The main differentiator I'm exploring is the integration between physical measurements and circuit design.

I've developed a functioning PCB prototype, firmware, and mobile application. The core DMM and measurement-to-calculator workflow are working, while the component identifier is still being refined.

I've attached a short demonstration showing how I use actual measurements to design and verify a voltage divider circuit.

Where I'm at commercially:

  • Target retail price: ~$89 for the DMM and app.

  • Preliminary component BOM target: under $35.

  • Business model: Hardware sales, with no software subscription.

  • Potential future revenue: Optional expansion modules and educational bundles.

  • Target customers: Electronics students, hobbyists, and makers.

I've already conducted some initial customer discovery around the problems I'm trying to solve. Now I'm working on validating willingness to pay.

I'd particularly appreciate advice from people who have brought hardware products to market:

  1. Does this seem like a product with a plausible commercial opportunity, or is the market already too saturated?

  2. If you regularly work with electronics, would the integrated software justify purchasing another measurement device at approximately $89?

  3. At this stage, what would you consider convincing evidence of demand before investing in a small beta production run?

  4. Are there any obvious issues with my pricing, positioning, or business model that I should reconsider?

I've personally funded development so far, and I'm trying to be careful about committing more money without better evidence of customer demand.

I'm not selling anything or taking preorders. I'm genuinely interested in learning whether this could become a viable business or whether it would be better kept as a personal engineering project.

I'd appreciate any insights, especially from those who have navigated this stage before.

Thanks!


r/hwstartups • • 14h ago

Building the programmable power supply I wish existed

Post image
140 Upvotes

Hey all, been a long-time lurker here, finally posting. I got so tired of the pile of wall warts and power strips for my music gear, I'm building a programmable power supply: 7 isolated DC channels with barrel jacks: configurable voltage, polarity, and max current settings. Also a four port USB hub, and a 100W USB-C charge port for a laptop or tablet. With all of it powered by a single USB-C power brick like you use for your laptop today.

I have a music solo act where I play live, and had some close calls with unplugged power bricks during soundchecks. I finally had it and started asking around on popular forums on how the heck other people solved this.

Most the answers I got was the same approach I already took, or a me-too-wish-this-existed response. So started designing it.

It's still in the early stages (thus the renders), but the first pass of the enclosure is designed. Have the main layout done. Now getting the first critical path board fabbed and shipped here in the next week.

Also trying something a little different with this product by designing it in the open, with weekly videos tracking how the product development is going, both the wins and the setbacks. It's kinda scary to develop like this as it's very vulnerable, but it's also awesome to share with others how our tiny team goes about building new products.

I'll aim to post here regularly with updates if there's interest. Otherwise we'll be posting updates on the blog at https://tonicaudio.com/blog and via YouTube: https://youtu.be/9xP5pFiPCFk

(Mods: if these links are against the rules, please let me know and I'll remove them. Def not trying to be spammy!)


r/hwstartups • • 15h ago

brevet d'invention au Maroc

0 Upvotes

Bonjour, je souhaite protéger mon projet, qui est une invention dans le domaine de la sécurité industrielle. Je voudrais connaître les étapes nécessaires pour déposer un brevet au Maroc, les documents requis ainsi que le coût de cette procédure. Merci pour votre aide


r/hwstartups • • 21h ago

Индекс хаоса команды: сколько денег и вкладок сжирает ваш стек

Thumbnail reddit.com
1 Upvotes

r/hwstartups • • 21h ago

Индекс хаоса команды: сколько денег и вкладок сжирает ваш стек

Thumbnail reddit.com
0 Upvotes

r/hwstartups • • 23h ago

London hardware founders: how are you funding growth? Free in-person roundtable, 30 November

6 Upvotes

London hardware founders: funding growth without giving up more equity? Free in-person roundtable, 30 November

Hi everyone! If you’re building a hardware business, how are you funding manufacturing and customer deployments without tying up the equity you need for hiring, product development and runway?

I’m Faith, founder of Uptime Finance. I’m working with six design partners to understand this problem and help hardware companies explore non-dilutive financing.

On 30 November, I’m hosting an in-person roundtable at Antler’s London offices, bringing hardware founders and finance providers together to discuss:

  • Financing equipment and deployments as you move from pilot to commercial scale.

  • What lenders need to see before they’ll fund you.

  • How contracts, commercial models and operational data can help unlock financing.

It’ll be an open discussion where you can bring your own challenges and meet other founders working through similar questions. Particularly relevant if you have proven technology and deployments to fund over the next 12 months, whether you sell, lease or offer hardware as a service.

Free entry, pizza and drinks.

Details and registration: https://luma.com/zx42d0t4

Would love to meet some of you there!


r/hwstartups • • 1d ago

Sanity check on my China sourcing & NPI setup (CNC prototyping -> Aluminum Die-Casting): Upwork NPI engineer + bilingual coordinator + strict NNN. Where are the blind spots?

0 Upvotes

Hi everyone,

I’m preparing to move a physical hardware product—specifically aluminum components transitioning from CNC machined prototypes to mass-production aluminum die-casting—in China (Guangdong/Pearl River Delta area). After dealing with opaque intermediaries in the past, I’m setting up a more transparent, checks-and-balances sourcing structure and would love a sanity check from folks who have actually done this on the ground.

Here is my current plan:

  1. Hiring an independent NPI Engineer via Upwork: I plan to interview candidates over video calls to vet their specific experience in aluminum die-casting DFM (draft angles, wall thickness, gating/venting), tooling, and QC, and hire one directly via Upwork milestones/hourly to manage technical specs and factory communication.

  2. CNC Prototyping to Die-Casting Factory Sourcing (with anti-kickback rules): I’ll have the NPI engineer shortlist 2–3 suitable factories capable of handling both the pre-tooling CNC samples and the transition into die-casting tooling/production (or an optimal split). To avoid hidden kickbacks or collusion, I’ll require itemized, transparent quotes—including clear mold ownership terms—and evaluate multiple options rather than blindly accepting one recommendation.

  3. Separate "Eyes & Ears" Coordinator: I’m hiring an independent Japanese-Chinese bilingual investigator/coordinator (separate from the NPI engineer) to run official corporate registry background checks (e.g., Qichacha/Tianyancha), verify business licenses (ensuring they actually own die-casting/CNC machinery rather than being trading companies), and act as an independent liaison/on-site witness.

  4. Legal & IP Protection before sharing CAD: Before sending any STEP files or drawings, every factory must sign a bilingual (Chinese-governing) NNN agreement under Chinese law/jurisdiction, stamped with their official red Company Chop (公章)—no English-only NDAs.

My questions for those experienced with China manufacturing / die-casting:

  • Does this separation of duties (NPI engineer vs. independent coordinator) actually work in practice, or does it create friction/confusion on the factory floor?

  • For aluminum die-casting specifically, what are the subtle red flags when interviewing an independent NPI engineer on Upwork to ensure they aren't secretly taking commissions from tooling/die-casting shops?

  • Are there any major blind spots in this CNC-to-die-casting workflow that I’m missing before I start interviewing?

Appreciate any blunt feedback or war stories!


r/hwstartups • • 1d ago

Searching for interns and potential co founders (only come if ur willing to take a bet on the future of chip design)

Thumbnail reddit.com
0 Upvotes

r/hwstartups • • 1d ago

Sto costruendo un device da zero usando praticamente solo l'IA.

Thumbnail reddit.com
1 Upvotes

r/hwstartups • • 1d ago

Looking for a Hardware Engineer / Product Developer.

Thumbnail reddit.com
1 Upvotes

r/hwstartups • • 2d ago

Big prototyp test sell

3 Upvotes

I'm working on a product and have made the first prototype it's a simple product with a board, 3 plastic parts, batteri springs and cabling. My initial thought is to start selling them as 3d printed parts, mount all the things myself, then if I sell 100 a month then I'll look into trying to make molds of one of the plastic parts, if I sell more than say 150-200 per month I will have some one else doing the assembly. But maybe none of these steps will come to pass. Have anyone done a similar process, or did/would you go straight to molds?


r/hwstartups • • 2d ago

Automated Instant-Quote Platforms vs. Direct Engineering-Led Shops: An honest breakdown for EVT/DVT runs (from the factory side)

1 Upvotes

Hey everyone — full transparency up front: I help run an ISO 9001:2015 certified prototyping & low-volume shop in China (datumrapid.com). Since we constantly see hardware teams switching back and forth between big automated platforms (like Xometry, Protolabs, or RapidDirect) and smaller direct shops, I wanted to share an honest comparison of where each actually makes sense.

**Where big automated platforms win:**

- **Instant ballpark pricing:** If you need a budget number in 30 seconds for an internal slide deck, automated CAD parsers are unbeatable.

- **One-click convenience:** Great for simple 3-axis brackets where you don't need much back-and-forth.

**Where automated platforms struggle (and where direct engineering-led shops like ours fit better):**

  1. **Zero-context pricing on tight tolerances:** Automated parsers often penalize ±0.01 mm callouts blindly—or worse, route your job to an unknown subcontractor who misses a critical mating bore. With a direct shop, an actual manufacturing engineer reviews your STEP + 2D PDF first and tells you *where* you can relax tolerances to save 30% without hurting function.

  2. **Bridge Tooling & Urethane Casting (10–1,000 units):** Platforms treat every part like a commodity. For DVT enclosures, silicone vacuum casting or 7075 aluminum bridge molds require real human judgment on parting lines, draft angles, and Pantone/RAL surface finishes—plus direct feedback when you inevitably do an ECO revision.

  3. **Accountability & SOPs:** Instead of wondering which random shop got assigned your order, working directly with an ISO 9001:2015 audited shop means you see the actual shop-floor setup, CMM inspection data, and pre-shipment photos before parts board the plane to North America or Europe.

**The trade-off with us:**

We don't have an instant 10-second AI price widget on our site—you email your specs or drawings to an engineer ([email protected]) and get a real DFM review + quote within 24 hours.

Happy to answer any questions about sourcing CNC, urethane casting, or bridge tooling overseas—or feel free to roast our site (`datumrapid.com`) if you have feedback on what engineers want to see!


r/hwstartups • • 2d ago

Offering free 30-min industrial design consultations / feedback

5 Upvotes

Hey everyone 👋

I’m an industrial designer working on physical tech products and smart hardware.

I’d love to give back to the community and offer group members a free 30-minute consultation and brainstorming session about

🔹 Design & development strategy for phyical tech product

🔹 Conceptual design with AI and advancing to functional POC prototype for demos

🔹 Ergonomics & usability & UX (for robots also)

🔹 Full product integration & geometric simulations

🔹 Integration of 3D printing in the entire process

Feel free to grab a slot directly on my calendar:

https://calendar.app.google/rmQGCdLQaWZXkTBT7


r/hwstartups • • 2d ago

👋 Welcome to r/SemacoLab - Introduce Yourself and Read First!

Thumbnail reddit.com
0 Upvotes

r/hwstartups • • 3d ago

After 12 months, our Lamps is on their way to meet their 1st owners (and still open source)

83 Upvotes

About a year ago we had a thought. Why not give AI a body? Something small enough to sit on your desk and fun enough that you’d still want it there after a week.

We were already chatting with AI on our phones and computers all the time. What would it feel like if it could sit next to you and turn its head when you spoke?

So we 3D-printed an arm, put five servos and a light ring on it, and called it Lamp.

12 months later, the first batch made it through customs and into our California distribution center. And the funny story is we had to explain that these were not a bunch lamps, but full robots call “Lamp”

Getting five servos to move on our bench was one thing. Sending them to someone else’s desk meant thinking about stuff like what happens when they change their Wi-Fi. In the latest build, Lamp brings back its setup hotspot if it loses the network it knows, so you can reconnect it without a factory reset.

In the last post I mentioned the Lamp you could run on your laptop. There’s now a 3D one on Linux that runs the same motion code as the real Lamp. And when you’ve got the hardware, you can push a skill straight from the SDK and say yes at the Lamp to install it.

The fun part has been hearing what people want to build. One person wants a greeter for their shop. Another wants to use Lamp in a research lab. Some just want a body for the agent they already work with. If you pair Lamp with Harness (one of our other products), you can ask it out loud to pass a task to Claude Code on your computer and hear the result back at your desk.

Lamp is still open source and we update it regularly. If you like to tinker, fork the repo and have at it (for the hardware, it's here)

If you’ve got a Lamp coming, what's the first thing you'll teach it.


r/hwstartups • • 3d ago

Sock Launcher Machine Market Research

Thumbnail
docs.google.com
1 Upvotes

Hello good afternoon, inee you guys and gals help to answer this quick survey for college.

thank you so much for helping me out.


r/hwstartups • • 3d ago

only making 150 pieces. what route would you take?

1 Upvotes

this product is supposed to be limited, so increasing it to 1000 pieces just to make manufacturing easier kinda defeats the entire idea. maybe 150 first run, possibly 250. mixed materials, nothing electronic or super technical. i found a couple smaller manufacturers on alibaba that were open to doing sample and lower quantity work, which made me realise this isnt as impossible as i first thought. would you still use a normal factory for something this small? local fabricator? small contract manufacturer? the setup cost is the part im trying to understand. paying more per unit is fine. paying for some giant tooling process that only makes sense at 10k units obviously isnt. curious how limited edition brands normally handle this.


r/hwstartups • • 3d ago

Nexo Lab un laboratorio tecnologico che progetta e realizza sia prodotti digitali che fisici, sviluppando sia hardware che software e firmware.

0 Upvotes

Dal concept al prodotto finito: piattaforme digitali, dispositivi connessi e sistemi integrati, tutto sviluppato in house.
Chi è Interessato?


r/hwstartups • • 3d ago

What is a realistic MOQ for a custom silicone product? I'm starting a small brand and don't want to order thousands of units.

0 Upvotes

There isn't one universal MOQ for custom silicone products. It depends quite a bit on the product design and how it needs to be manufactured.

I would look at a few things before focusing on the quantity:

1. Mold cost

A custom silicone product usually needs tooling. If you're only ordering a few hundred pieces, the mold investment is spread across a relatively small number of units. That can make the effective unit cost much higher.

Ask for the tooling cost separately from the product price.

2. Material requirements

The material, color and required performance can affect the production cost. A material option that is cheaper may not be appropriate for your intended application, so don't reduce the specification without checking what it means for product performance.

3. Design complexity

A simpler design may be easier to tool and manufacture than one with complicated geometry or several functional features.

This is why it helps to get a DFM (Design for Manufacturing) review before paying for a mold.

4. Sample and initial production

Ask whether the supplier can evaluate a sample-production route or a smaller initial batch. Be clear about whether the sample tooling is suitable for later mass production; the two are not necessarily the same.

One more thing: don't assume that a supplier advertising "low MOQ" is automatically the best choice. A low minimum quantity can come with a much higher unit price, limited material options or other trade-offs.

Before requesting quotes, prepare a sketch or 3D file, approximate dimensions, intended use, material requirements and your target first-order quantity. You'll get more useful answers than asking only, "Can you do 300 pieces?"

The important question is not just whether a supplier accepts your order quantity. It's whether the whole project makes economic and technical sense at that quantity.


r/hwstartups • • 4d ago

Offering help on RFQs for Plastic Parts

1 Upvotes

Had a wearables start-up and dealt with many injection molders across the world (UK, USA, China, India & Mexico) and have a couple contacts.

Happy to help any hardware start-ups looking for quotes on injection molded parts. I've been through this painful process myself and have some free time now to help other people out.

Dm if you need help


r/hwstartups • • 4d ago

Planning a hardware or supply chain trip to Shenzhen? Here is a practical prep checklist and factory vetting framework.

0 Upvotes

If you are planning a trip to Shenzhen to evaluate hardware partners or electronics suppliers—whether tied to an upcoming conference like APEC 2026 or a dedicated sourcing trip—simply touring factories without a focused technical objective often yields low-value results.

Here is a structured framework and checklist to help hardware founders, engineers, and supply chain teams make the most of a visit:

  1. Preparation Checklist Before Flying

Before scheduling supplier meetings, compile a concise project brief:

* **Project Stage:** Clarify whether your product is a conceptual idea, working prototype, or existing commercial hardware.

* **Expected Volumes:** Are you sourcing small pilot batches, prototype assemblies, or full production runs?

* **Technical Files:** Organize Gerber files, BOMs, mechanical drawings, or product specs.

* **Target Market & Compliance:** Define target sales regions and expected regulatory compliance requirements.

* **Objective:** Specify whether you are assessing PCB/PCBA facilities, exploring prototyping services, or evaluating OEM/ODM platforms.

*Safety Tip:* Save sensitive proprietary designs until initial technical suitability is confirmed and confidentiality options are evaluated.

2. Vetting PCB & PCBA Suppliers (Questions Beyond Price)

When meeting electronics assembly and board manufacturers, avoid focusing strictly on unit pricing. Ask about:

* PCB fabrication constraints and automated SMT assembly capacity

* Component sourcing procedures and component substitution controls

* Inspection protocols (AOI, X-ray, functional testing) and quality traceability

* Readiness to support small-batch prototypes before scaling

3. OEM vs. ODM Requirements

* **OEM Projects:** Focus on whether the factory can meet your exact build specifications, quality standards, and testing procedures.

* **ODM Projects:** Focus on customizing an existing hardware platform. Clarify IP/design ownership, customization boundaries, and testing responsibilities early.

4. Sample 1-Day Focused Itinerary

* **Morning (Market & Component Research):** Visit electronics hubs like Huaqiangbei to assess component availability and market trends (remember: market findings still require formal supplier qualification).

* **Midday (Engineering Alignment):** Review product specs and align on specific technical questions before the plant meeting.

* **Afternoon (Prearranged Supplier Audit):** Conduct an on-site visit to inspect assembly lines, quality control stations, and engineering setups.

* **End of Day (Evaluation):** Log findings, identify remaining engineering risks, and map out follow-up steps.

For anyone who has conducted factory audits or component sourcing trips in Shenzhen or the surrounding Greater Bay Area: what pre-trip preparation or specific technical question saved your team the most trouble later in production?