The whole grow, in one place. The story behind Growgoyle.

About Growgoyle

Software engineer. Commercial grower.

I’m Eric Klamer, a senior software engineer and integration specialist with a background in hardware systems and IT. I work on MAGI ERP, manufacturing software used by businesses of different sizes around the world. I also operate a commercial cultivation facility in Michigan.

Software people depend on every day

My work includes designing business-system integrations and working directly with shop-floor teams to improve how their jobs get done. Two examples:

Tracking materials through outside processing

At one manufacturer, workers were using spreadsheets and printed orders to organize material going to an outside processor. Matching what came back was difficult. There were mistakes, surprises, and no dependable view of where everything was.

I worked with the shop-floor team and designed and implemented a custom barcoding workflow: scan material out to the vendor, receive it back into the operation, and keep its status visible throughout the process. The team could see what had gone out, what had returned, and what was still with the processor.

Connecting MAGI ERP with sales channels

I also designed and built MAGI Channel Hub, connecting MAGI ERP with online sales channels. It handles the exchange of orders, inventory, shipments, refunds, and cancellations, with monitoring to identify interrupted synchronization. These are the details businesses rely on to fulfill orders and keep their records straight.

Why I built Growgoyle

In my own grow, the work was spread across schedules, spreadsheets, messages, and whatever I remembered. I needed a better way to plan crops, coordinate the crew, maintain equipment, and find the record of what happened.

I built Growgoyle to bring that operation together: plan crops and the week, assign the work, keep maintenance on the calendar, and save the room’s readings, photos, notes, and results where we can find them. Analysis helps us investigate the record and decide what to carry into the next run.

Building and maintaining the service

I build, host, and maintain Growgoyle. Hosting, updates, monitoring, and ongoing maintenance are part of my responsibility for the service. My hardware systems and IT background informs that work alongside software development.

If you’re evaluating Growgoyle for your operation, talk directly with me about the workflow, setup, and support you need.

What Growgoyle Actually Does

  • Crop and weekly planning: Keep rooms, cultivars, crop timing, and assigned work on a shared schedule.
  • Daily work and maintenance: See who owns the job, what got done, and what still needs attention.
  • Connected room records: Keep notes, photos, feed and runoff records, sensor readings, and harvest results with the crop. Direct connections support Pulse, TrolMaster, and AROYA; supported CSV imports cover other setups.
  • Run review: Compare batches and use photo analysis and investigation leads to decide what to check or change. Recommendations support the grower’s judgment; they do not prove causation or guarantee a yield gain.

Who It’s For

Growgoyle is built for commercial cultivators: one grower keeping a facility moving, a crew working across rooms, or an operator managing several sites. Start with an active crop and the work in front of you. You do not need to wait for the next harvest to get the schedule and maintenance under control.

See How It Works

Explore the live, view-only demo without signing up. To plan crops and try the workflows with your own records, start a 30-day complete-product trial with no credit card required.