Manufacturing · Embedded Systems Company Management Software

One project record for boards, firmware and the engineers behind them.

One project record holds the statement of work, requirements, change requests, schematic and layout revisions, bills of materials, firmware releases, prototype lots, defect lists, engineer time and milestone invoices. A board serial shows its layout revision and flashed firmware, and the project lead sees effort against plan before a customer asks for one more interface.

Share your requirements

Work packages, day rates per engineer grade and project types entered at the start
Open projects, hardware revisions and unbilled milestones brought across
Changes to task or release fields made by GullySystem staff after you ask

Design houses and firmware firms hold statements of work, schematic and layout revisions, firmware releases, prototype lots, bench defects and engineer time together. A board serial shows its layout revision and flashed release. A change request shows its days and cost. A closed milestone shows an invoice due.

Where it breaks today

What goes wrong before the software.

Unclear revision pairing

Nobody noted which firmware release fits which board revision, so the layout sits on revision C and the code on release 1.4 while the unit at the customer carries an older mix. Support guesses.

Unrecorded scope changes

Small asks add up. A SPI sensor or a second UART is agreed on a call and built into the next release, but no change is logged against the statement of work. Those engineer days go unbilled.

Prototype lots without serials

Boards return from the assembly partner in lots of ten or twenty, and the fitted parts, the serials and the flashed bootloader are known to one engineer. Nobody else has the list.

Timesheets from memory

Engineers split days across customers and fill the sheet on Friday from memory, so a fixed-price project cannot be compared with the effort it took. The next quote repeats the same error.

Bench findings in chat threads

A brown-out reset found at the bench is posted to a message thread, and weeks later nobody can say which board revision showed it or whether the fix reached the next release. The thread has scrolled away.

Milestones not invoiced

Payment is tied to design review, first boot and acceptance test, yet accounts hear about completion late and invoices wait until someone remembers. Cash arrives well behind the work.

How it runs

How the work flows through it, step by step.

1
Scoping and quote
A customer brief becomes work packages with engineer days, bought-in modules and risks, and the quote carries its revision. The accepted quote opens a project with its milestones.
2
Design
The customer signs off the requirement list first. After that, every schematic and layout revision is logged with its parts list and Gerber files, and design reviews are minuted against that revision.
3
Prototype build
A lot is ordered from the assembly partner, and boards arrive with serial numbers and the fitted parts recorded against each one. Short runs stay traceable from reflow to bench.
4
Bring-up and firmware
Engineers flash a firmware release onto a serial through the JTAG or SWD programmer and log what the scope and the serial console show. Defects move from open to fixed to verified.
5
Change handling
A late request becomes a change with its days, its bought-in cost and its effect on the delivery date, which the customer approves or declines in writing. Nobody starts before that.
6
Acceptance and handover
Release notes, design files, the final bill of materials and test reports are issued as a handover set, the last milestone is invoiced, and then the project closes.

Modules

What is inside.

Every module can be switched on, left out or changed to match how your team already works.

Statements of work and quotes

Build quotes from work packages, engineer days and bought-in modules, keep every revision, and turn the accepted one into a project with its milestones and payment stages.

Requirements register

List each requirement with its source and status, and link bench tests, schematic pages and firmware tasks back to the line they satisfy. Orphaned tasks show up.

Change requests

Log late asks such as an extra I2C sensor with their days, cost and effect on the delivery date. Approval is recorded before any work starts.

Hardware revisions and bills of materials

Store each schematic and layout revision with its own parts list, and compare two revisions to see the swapped components, footprints and approved alternates at a glance.

Firmware release register

Each release carries its version, branch, checksum, notes and the board revisions it supports, and a serial shows which release is flashed on it through the bootloader.

Prototype lots and serials

Track lots from the assembly partner, where every board has a serial, a fitted-parts record and a bench test status. Short runs of five boards are covered too.

Defect and test log

File defects against a serial and a release, with the steps to repeat them on the bench, and close each item only when a passing retest is recorded. Nothing hides in chat.

Engineer time sheets

Hours go against project tasks as the work happens, so planned effort sits beside actual effort for every work package. The sheet is filled at the bench, not rebuilt on a Friday.

Lab equipment register

Oscilloscopes, logic analysers, JTAG programmers and development kits have a holder, a location and a calibration due date, and reminders reach the lab owner.

Component purchasing

Raise orders for modules, development boards and test fixtures under a project code. Goods received are matched to the order line, and anything held back for that project is named there.

Milestone invoices

A closed milestone prompts an invoice for the agreed amount with tax settings applied, and balances by customer list the oldest unpaid invoice first.

Solutions inside

The business modules it is built from.

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

Estimate/Quotation Management
A quote is built from work packages, engineer days and bought-in modules, and the accepted revision opens the project with its milestones in place.
Project Document Management
Customer briefs, approved requirements and design review minutes are filed under the project, so each task points back to the requirement line it satisfies.
Bill of Materials
Each schematic and layout revision holds its parts list, and the difference between two revisions shows which components and footprints were swapped.
Batch and Serial Tracking
Every board from the assembly partner receives a serial, so its fitted parts, firmware load and bench test result can be found later.
Quality Control
Bench results are recorded against a board serial and release, and a defect moves to verified only after a passing retest on the same serial.
Project Time Tracking
Engineers book hours to tasks within a work package, so planned effort can be compared with actual effort while the project is still running.
Asset AMC Tracking
Oscilloscopes, programmers and development kits carry a holder, a location and a calibration due date, with reminders to the lab owner.
Invoice Management
A milestone that closes prompts an invoice for the agreed sum, and each customer’s balance lists the oldest unpaid invoice first.

Services

How we would put it in.

Setup, data migration, integrations and anything built on top.

Who uses it

One system, each person sees their part.

For project leads

See effort against plan, open changes and defects per release, then decide whether a late request fits the schedule before the customer expects an answer.

For firmware and hardware engineers

Open assigned tasks, log time, file defects against serials, and read the requirement behind each task, all without leaving the lab bench.

For test engineers

Record results per board serial and release, then mark a fix verified once the retest passes, so brown-out and EMC pre-compliance findings stay attached to the right revision.

For account managers

Track quotes, change approvals and customer sign-offs, and keep release notes ready to share the moment a buyer asks for the latest build.

For accounts

Invoice closed milestones and hourly work, then chase balances by customer. Cash follows the work.

Reports

The numbers the owner asks for.

Effort against plan by project and work package
Change requests raised, approved and billed
Open and verified defects by firmware release and board revision
Prototype lots with serials, fitted parts and bench status
Milestones closed and awaiting invoice
Oscilloscopes and programmers due for calibration
Quotes won and lost by customer and project type

Good fit

Who this is built for.

Design houses that build boards and firmware for other companies
Product firms with an in-house team that ships its own devices
Firmware consultancies working on RTOS, bootloader and driver projects
Companies that own a lab and a small prototype line
Teams that move from prototype lots to a first pilot batch

Honest answer

When it is not the right choice.

A single freelance engineer who works on one project at a time can manage with a task board and a spreadsheet.
A company that only writes application software, with no boards, will find a general project and time system closer to its work.

Made to fit

Adapted to your business before it goes live.

You are not handed a login and left to it. The product is set up around your records, your people and the tools you already use.

Work packages and day rates

Your standard packages, engineer grades and day rates go in first, in your currency and units, and your project leads review them before the first quote.

Release fields

Version scheme, branch names and the board revisions a release supports are set the way your team writes them, down to the tag format.

Milestone terms

Payment stages for each customer, such as design review, first boot and acceptance test, are entered with the tax settings that apply and reviewed with your accounts staff.

Projects brought across

Your trackers and spreadsheets supply the open projects, earlier quotes and milestones not yet billed. A project lead then compares several records with the firmware and board-design originals.

Hosted by GullySystem

Engineers log in from the lab, from home or from a customer’s site, and GullySystem looks after the hosting.

Works alongside

Email
Messaging
Accounting export
Source repository links
Spreadsheet import
Document storage

Common questions

Questions owners ask before a demo.

Can it show which firmware a board runs?

Yes. Each board serial lists the release flashed and the layout revision it is built on, so support questions start from that pair and never from someone’s memory.

How are late requests priced?

A change request carries extra engineer days, bought-in cost and the effect on the delivery date. The customer approves it before engineers begin, and the approved change adds to the billable total of the project.

Can we run fixed price and hourly projects?

Yes. Fixed-price work bills on milestones, hourly work bills booked time, and both keep planned effort beside the real figure.

Does it replace our code repository?

No. Source code stays in your repository. The release register holds version, notes and supported boards, with links back to the repository.

What about our lab equipment?

Each instrument has a holder, a location and a calibration date, a reminder arrives ahead of each due date, and every past loan of a kit stays listed on that instrument.

Can customers log in?

If you choose. A customer sees milestones, defects and releases for their own project only, and you decide how much detail is visible.

Can past projects be loaded?

Yes. Your running projects, quotations and milestones not yet invoiced are brought in, and a project lead checks a few against the originals.

How is it priced, and can I see it first?

You see it first, after a conversation about how your team works. The walk-through uses project and release names from your own business, and the quotation reflects users and import work.

What if our process changes?

GullySystem staff adjust the stages and fields on request, so a new test phase or release type can be added without disturbing projects already running.

Wondering what it would cost? Share your requirements and an engineer will come back with a scope.

Industries

Businesses that use this.

Embedded systems companies

Related products.

Book a demo

See Embedded Systems Company Management Software with your own data.

Tell us how you run things today. We’ll show you the parts that matter to you and say plainly what would need changing.

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.