Pilot stage · Bengaluru, India

PCB prototyping in Bengaluru, from design files to a tested first build

An engineer reviews your files, we coordinate parts and assembly, and we agree a test plan before the first board is built. Start with one board or two; build more once the design is proven.

  • One board or ten, sized to the milestone
  • Engineer-signed design review
  • A test plan before the first build
  • Every file stays yours
U1J1J2REV A

Build · 2 units

Queued: starts once the review is signed.

Assembling. Photo sent on WhatsApp.

Tested: 2 of 2 pass the agreed plan.

Engineering review

MTR-DRV · Rev A

  • Files and BOM complete
  • Known risks listed
  • Test plan agreed
  1. Design
  2. Review
  3. Build
  4. Test

Review the design

Files · BOM · known risks

Coordinate the build

Parts · partners · scope

Define the proof

Test steps · results · handoff

Send files from

  • KiCad
  • Altium
  • EasyEDA
  • Flux
  • tscircuit
  • Gerber + BOM + pick-and-place
  • STEP for enclosures

Why the first build gets stuck

A PCB quote is one step. A useful prototype needs a plan for the whole first build.

AI and EDA tools now produce Gerbers in an afternoon. Setup, sourcing and testing still need an owner.

01

Setup at small volumes

Design files, board revision, assembly scope and preparation all need confirming before even a one-board order.

02

Parts set the real timeline

Component availability and substitutions shape the schedule, so the BOM is checked before any date is committed.

03

Testing needs a plan

Agree what the first board must prove, how it is checked and what results come back, before it is built.

How it works

A clear path from design files to a tested first board

Scope the work, align the build and agree what success looks like before the order starts.

  1. 01

    Share context

    Your milestone, design revision, BOM and current blocker.

  2. 02

    Review readiness

    A free DFM check, then an engineer’s review: missing inputs, technical questions, known risks.

  3. 03

    Agree the scope

    Quantity, build, test plan, assumptions, date and quote, in writing.

  4. 04

    Build and learn

    Boards built and tested, with results, exceptions and next steps recorded.

For a small build, we aim for five working days from frozen, reviewed files with every part in hand, with updates and photos on WhatsApp along the way.

Capabilities

From a first board to a pilot run

Build as few boards as the milestone needs. One or two are often enough to prove a design.

Free DFM check

Send Gerbers, a BOM and a pick-and-place file. A written list of manufacturing issues comes back in one working day.

Engineering review

A written verdict signed by an engineer: schematic, layout, power, interfaces, DFM and known risks.

Multi-board systems

Robots and other systems of several connected boards, reviewed and built together, with the interfaces between them checked.

From idea to device

No files yet? A design built from proven blocks, reviewed and signed by an engineer, then built and tested.

Pilot runs and production

Once the design is proven, pilot runs and production through partner lines, on the same build record and tests.

Why Qohor.ai

One engineering-led owner for the first build

An engineer’s signature

AI speeds up the checks; an engineer reads every design and signs the result.

Parts, partners and assembly in one place

One team coordinates fabrication, sourcing, assembly and test, so nothing falls between vendors.

A test plan before the build

What the first board must prove, how it is checked and what comes back, agreed up front.

Your files stay yours

Every file, revision and test result comes back to you.

Who it’s for

For teams building what comes next

Early product teams and engineering leads turning an electronics design into a demo, an evaluation or a design-review milestone, including designs from AI tools such as Flux and tscircuit.

  • Robotics
  • Connected devices
  • Wearables
  • Industrial electronics
  • Embedded products
  • Makers and students

What we’re building next

AI design that ships

In development

AI tools can already draw a board. Ours will only draw boards we can build: designs from proven circuits and parts we stock, checked against the same rulebook as every board we review, and signed by an engineer before anything is made.

  1. 01

    Describe it

    Say what the device must do, in plain words.

  2. 02

    Design from proven blocks

    Schematic and layout from circuits we have built before and parts on our shelf.

  3. 03

    Engineer-signed

    The same review and rulebook as every board we build, with KiCad files you can edit.

  4. 04

    Order the build

    Quote, build and test in one flow, starting from one unit.

Every board we review, build and test adds to the rulebook and to the library of proven blocks those designs come from.

How pricing works

Every build is quoted from your files

The board, BOM, quantity, sourcing, setup and test scope decide the cost, so the quote follows the free DFM check. You can start with a single board.

Free DFM check
₹0
Engineering review
from ₹9,000 per board
Prototype build
quoted per build, from one unit
Prices ex-GST, on a GST invoice. Design responsibility stays with you; re-spins are priced per changed board.

Good to know

Questions founders ask

How many boards do I need to order?

As few as one. One or two boards are often enough to prove a design; build more for testing, demos or investors once it works.

What affects prototype cost?

The board, the BOM, quantity, sourcing, setup and test scope. Setup and stencil costs are much the same for one board or ten, so each extra unit adds less than the first.

How fast can you build PCB prototypes in Bengaluru?

For a small build we aim for five working days from frozen, reviewed files with every part in hand. Design readiness, parts and partner capacity set the date, so it goes into your written scope after the review.

Is Qohor.ai taking builds now?

We are at the pilot stage in Bengaluru, with pilot conversations and partner discussions under way. Send your files and we will tell you what we can take on, and when.

Do you design boards with AI?

Today, AI checks every design against our rulebook and an engineer signs the result. AI design from proven, stocked blocks is in development; join the early-access list to try it first.

Which files do you need?

Gerbers (or ODB++), a BOM with manufacturer part numbers, a pick-and-place file and your firmware. Native KiCad, Altium or EasyEDA projects help the review, and a STEP file helps the enclosure.

Do you review the design before you build it?

Yes. Every build starts with an AI check against our rulebook and an engineer’s review. You can also order an engineering review on its own.

Who is responsible if the design has a flaw?

Design responsibility stays with you. Our review is written and signed, so you know exactly what was checked, and re-spins are priced per changed board.

Can a prototype go on to production?

Yes. Once the design is proven, pilot runs and production go through partner lines, using the same build record and tests.

Who owns the design files?

You do. Every file, revision and test record comes back to you.

Pilot conversations open in Bengaluru

Have a prototype milestone coming up?

Bring your files, questions or blocker. We start with a clear scope and a free DFM check.