Skip to main content
GullySystem
Manufacturing · Software for embedded systems companies

Link every firmware tag, board revision and bring-up finding to its project.

An embedded systems company sells design hours plus the boards and firmware that come out of them. This software ties the statement of work, schematic revisions, firmware tags, prototype lots, bring-up findings and engineer timesheets under one project, so a customer’s question about a unit gets a single answer.

Share your requirements
At a glance

A project starts as a requirements document and ends as a board running a tagged firmware release. In between come schematic revisions, Gerber packs, prototype lots from the assembly partner, errata notes from the silicon vendor and a customer who changes their mind twice. Each lives in a different place.

This software keeps them together under the project. Firmware engineers, the layout designer, the project lead and the account manager then read one history, and the question of which bootloader image runs on which board revision has a plain answer.

How the work runs today

The project lead opens the day with build status, and revision B boards have just come back from the reflow line at the assembly partner. Two of five fail to boot over SWD. The firmware team holds a release candidate and waits for a clean unit before signing it off. Engineers book hours for layout, driver code, device tree edits and test scripts against the task. Then the customer asks for an extra I2C sensor, and the lead must see what that does to the schedule before replying.

Test results land in a defect list with the firmware tag and board serial beside each entry, while oscilloscopes, logic analysers and J-Link programmers carry calibration dates to watch. Loan slips for development kits go missing. Invoices follow the milestones in the statement of work, so nobody has to dig through old emails to learn what was agreed with the customer.

Where it breaks

What goes wrong for embedded systems companies without a proper system.

Mixed-up revisions

Which build runs where? The layout is on revision C, the firmware on release 1.4, and the unit sitting on the customer’s bench carries an older image that nobody wrote down.

Scope creep unnoticed

A small extra, say a CAN transceiver, is agreed over a call and built in a week. With no change filed against the statement of work, the hours are absorbed and never billed.

Prototype lots untraced

Boards return from the assembly partner in lots of five or twenty. Only one engineer remembers the serials, the fitted parts, the rework wires and which firmware image went onto each.

Hours without projects

Engineers split days across several customers and fill timesheets on Friday from memory. A fixed-price job then cannot be set against the effort it truly took.

Test findings lost in chat

A brown-out reset is posted in a thread. Weeks later nobody can say which board revision showed it, or whether the fix reached the next release tag.

What the software does

What we would build for embedded systems companies.

Named the way your team already talks about the work. We start with whichever part the audit shows is costing you most.

Statements of work and quotes

Build a quote from work packages, engineer days and bought-in items such as evaluation boards, programming adapters and test fixtures. Older drafts stay on file, and once the customer signs, the accepted version turns into a project carrying its milestones.

Requirements and change requests

List what the customer asked for. A request that arrives later is logged as a change with its effect on days, cost and dates, then approved or declined in writing before anyone opens the editor.

Hardware revisions and BOM

Hold schematic and layout revisions with the matching bill of materials, and see which parts moved between revisions, including second-source substitutes and the footprint changes behind them.

Firmware releases

Record each release with its tag, branch, release notes, bootloader version and the board revisions it supports.

Prototype builds and serials

Track every lot from the assembly partner. A board’s record lists its serial, fitted components, rework notes and the image flashed at the factory.

Bring-up and test log

Defects are filed against a board serial and a firmware tag, and status moves from open to fixed to verified with the retest result kept beside it.

Engineer time and milestones

Hours go against project tasks and work packages. When a milestone in the statement of work closes, its invoice is raised.

Before you talk to a supplier

A requirements checklist for embedded systems companies.

What to cover, which reports to ask for and what to put to every vendor, ready to print or save as a PDF.

Open the checklist
Ready product

A product already built for embedded systems companies.

It is adapted to how your business works before it goes live, and anything your trade needs that it lacks is added then.

Embedded Systems Company Management Software

Quotes from statements of work, change requests, schematic and firmware revisions, prototype serials, bench defects, engineer time and milestone invoices for embedded design companies.

See the product
Solutions inside

The business modules embedded systems companies use most.

Each one is also available on its own, or inside a system built for you.

Services

The services behind it.

Business Process Automation

Approvals, reminders, follow-ups and reports that run on their own instead of on someone remembering.

Learn more

IoT and Edge Computing

Machines, meters and sensors feeding the same system your office uses, even when the network drops.

Learn more

ERP, CRM and Business Software Implementation

One record of stock, orders, customers and accounts, set up so your team opens it every day.

Learn more

Data Migration and Moving Off Spreadsheets

Data migration and spreadsheet replacement covers auditing existing files, cleaning and deduplicating records, loading them into a new system and reconciling the loaded result against known totals. Both systems then run side by side before cutover. Originals stay untouched.

Learn more
How it works

How the work runs from Bengaluru for your city.

  1. 1

    The audit, by call

    A screen-share and a look at the sheets, accounting reports and WhatsApp groups your team uses. No travel needed.

  2. 2

    A written proposal

    Scope, what we build first and the cost, agreed in writing before anything starts.

  3. 3

    Build in short rounds

    Working screens shared every few weeks. Your team tests them from your own office.

  4. 4

    Go-live, in person when it helps

    For data migration and training we can come to your city. Travel is agreed in advance.

  5. 5

    Support online

    Fixes, changes and hosting handled remotely by the same team that built it.

Our work

Software we have built and run.

We only name clients whose work is published. These are systems our team designed, built and supports.

All case studies
Pet care and veterinary services

PetSeva: matching owners to the right vet, at any hour

A two-sided veterinary platform where vets are searchable by specialisation and bookable outside clinic hours. It now carries more than 2,000 veterinary doctors.

Read the case study Paying guest accommodation

SAM Atithi Pavathi: bed-level occupancy as the source of truth

PG management software where allocation, rates and invoices are derived from bed-level occupancy and not maintained in parallel spreadsheets.

Read the case study School transport services

SAM Tours: school transport on a single ledger

Registration, fee collection, routing and finance write to the same records, closing the gap between journeys run and fees collected.

Read the case study
Common questions

Questions embedded systems companies ask before they call.

Can it link firmware to board revisions?

Yes. Each firmware release lists the hardware revisions it supports, and each board serial shows the image loaded onto it. A support question about a unit in the field starts from that exact pairing. No guessing.

Do you handle fixed-price and hourly work?

Both. A fixed-price project holds its milestones and invoices them as they close. Time-and-materials work bills the hours engineers booked against each task, and planned effort sits beside actual effort on both. Simple.

Can customers see progress?

If you want it, yes. A customer login can show milestones, open defects and release notes for their own project only, while internal layout files and rate cards stay hidden. What is shown is decided with you.

How are lab instruments tracked?

Each oscilloscope, programmer and development kit has a register entry with its location, current holder and calibration due date. Reminders go to the lab owner before the date passes.

What happens after I share my requirements?

An engineer reads what you send and replies within one business day. We then look at the software, spreadsheets and WhatsApp groups your business runs on today and write down what works, what slows your team down and what is missing. A demo login, a screen-share or a few screenshots are enough. You get a short written summary ordered by priority, with no obligation to hire us afterwards.

How much will the software cost?

We don’t publish a price, because it depends on what the system has to do. That first review settles the scope, and the cost goes into a written proposal before any work starts.

Related

Related industries.

Category

Part of a wider group.

Talk to us

Tell us how your business runs today.

A few lines on your spreadsheets, software and WhatsApp groups is enough. We reply the same working day.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements