Skip to main content
GullySystem

Daejeon · CountriesDaejeon’s research institutes and spin-off firms need tidy project, prototype and grant records.

Daejeon is Korea’s science city. Research institutes, KAIST and small firms that make sensors, instruments, embedded devices and defence parts gather at its science complex, and grants with reporting duties fund their projects. Invoices are in won. Project, build and compliance tools for such firms are built remotely by GullySystem in Bengaluru.

At a glance

The science complex is the centre of the city’s work. Research institutes publish results and young companies turn them into devices, so a small team may build a prototype, write a grant report and prepare a first batch together.

Grants shape the paperwork, because each project has milestones, expense categories and receipts that officials check closely before the next instalment of funding is released. Defence and instrument makers add parts lists and test records for their buyers. Missing data stops payment.

Around Daejeon

The districts, business parks and markets that matter in Daejeon.

Daedeok Innopolis

Research institutes, university labs and start-ups share one science complex, and staff can move between public projects and private ventures within the same year. Shared labs need sign-out records.

KAIST campus

The science and technology university feeds spin-offs and hardware teams, and equipment loans and student projects need clear ownership records. Students found companies young.

Government Complex Daejeon

Several national agencies have offices in this complex, and the contractors and consultants who work with them follow detailed reporting rules for every project. Paperwork follows the budget year.

Expo Science Park and Yuseong

A park left from the 1993 Expo and the Yuseong hot spring district draw visitors, which supports local hotels and cafes. Hot springs fill hotels at weekends.

How software gets chosen

How Daejeon businesses pick and use software.

Founders of small instrument and embedded device firms who report to grant officials as well as to customers.

Managers of defence component workshops who keep test results and parts lists for each delivery.

Where it breaks

Where Daejeon businesses lose time and money.

Grant receipts are sorted at the deadline

Spending is gathered in the last week before a report is due, and the finance lead spends two evenings matching receipts. Tagging expenses as they happen helps.

Prototype versions are not recorded

Teams rebuild boards and forget which parts list was used for which revision, so a failed test cannot be traced. A build register settles it.

Test data sits on lab laptops

Results are stored on the machine where the test ran, and a customer who asks for them must wait for someone to find the file. A shared record by serial number fixes it.

How it works

How the work runs from Bengaluru for Daejeon.

  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 Daejeon. Travel is agreed in advance.

  5. 5

    Support online

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

Make an informed decision

Make the scope specific to your business.

Work through a real example from your operation and agree the handoffs, controls and support the project needs.

Grant receipts are sorted at the deadline

Can the same receipt be allocated without counting the money twice?

Take an unallocated amount in “Grant receipts are sorted at the deadline” and apply it to the intended balance. Review the remaining amount and the original receipt reference together.

Background reading: ERPNext: payment allocation

Prototype versions are not recorded

Can someone correct a mistake without losing their earlier work?

Use “Prototype versions are not recorded” to test an incomplete submission with keyboard-only input. Check the error wording and retained values before signing off the screen.

Background reading: W3C: usable form validation

Common questions

Questions Daejeon owners ask before they call.

Can a small hardware firm track builds by serial number?

Yes. Each unit carries its revision, parts lots and test results, and the record opens from the serial number. We would agree the fields with your engineers first.

Can the grant report come from the same records?

Yes. If expenses are tagged to milestones as they are entered, the report becomes a view of that data, and we would match the layout your funder asks for. A call at noon in Daejeon is half past eight in Bengaluru.

What happens after I share my requirements?

We review your brief and clarify the work with you. 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.

Talk to us

Tell us what your Daejeon business runs on today.

Send a short note on the spreadsheets, software or WhatsApp groups your team depends on. We reply the same working day.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements