Your business shouldn't have to work around its software.
gifSolutions builds custom software around the systems your business already runs. We connect what you have, automate the work that falls between them and build the tools you can't buy off the shelf.
Where the week goes.
| What you see | What is usually behind it |
|---|---|
| The same order gets typed three times. | Each system was bought separately, and nothing passes data between them. |
| Quotes and invoices wait on one person. | They are the only one who knows which spreadsheet holds the current prices and how the two systems line up. |
| Reports take a day to put together. | The numbers live in four places, so someone exports each one and joins them by hand in Excel. |
| Your team works the way the software wants. | The package was built for an average company, and yours has pricing, approvals or steps it never planned for. |
What we build
Systems integration
We connect the software you already run, whatever it is, through its APIs and databases. Something entered once shows up everywhere it is needed, and nobody re-keys it.
Example A sales rep marks a deal won
- by handSales marks the deal won in the CRM.
- by handSales emails the quote to operations.
- by handOperations re-types the order into the ERP.
- by handOperations checks stock and the customer's credit.
- by handOperations emails a confirmation back.
- by handSales updates the CRM with the order number.
- by handSales marks the deal won in the CRM.
- automaticThe order is created in the ERP from the quote lines on the deal.
- automaticStock and credit are checked, and a failed check goes to operations.
- automaticOperations gets a message with a link to the order.
- automaticThe order status shows on the account in the CRM.
Steps done by hand: 6 today, 1 after.
What we build
- CRM and ERP sync. Accounts, contacts, orders and invoices stay the same in both, with one system named as the owner of each field.
- Event-driven integrations. An order, a payment or a status change in one system starts the next step in another.
- Middleware. A service that sits between your systems with logging, retries and alerts, so a failed record raises an alert and can be run again.
- Portals and dashboards. Screens for staff or customers that read live from the ERP.
How an integration works
An integration is software that reads from one system and writes to another. It runs on a schedule, or the moment something happens, such as a deal being marked won. It follows your rules for which system owns which field.
Every integration comes with a written map of what moves where.
What happens to the systems you have
You paid for your ERP and your team knows it. We work through its API where it has one, and through its database or exports where it doesn't. We only suggest replacing a system when that system is the problem.
Workflow automation
Quoting, order entry, invoice processing and approvals run on your own business rules, written in code. Your people handle the exceptions.
Example A customer emails a quote request
- by handInside sales reads the email and the attached parts list.
- by handThey look up each price in the price sheet.
- by handThey check stock and lead time in the ERP, part by part.
- by handThey type the quote into a Word template.
- by handA manager approves the discount by email.
- by handThey email the quote to the customer.
- automaticThe email and its attachment are read into a draft quote.
- automaticPrices and the customer's terms come from the ERP.
- automaticStock and lead times fill in.
- automaticA discount over the limit goes to the manager to approve.
- by handInside sales checks the draft and sends it.
Steps done by hand: 6 today, 1 after.
What we automate
- Quotes. A request comes in, and the quote is built from current ERP pricing and the customer's terms. It goes out after a person checks it.
- Order entry. Orders that arrive by email, PDF, web form or EDI are read and entered into the ERP.
- Invoice processing. Vendor invoices are matched to purchase orders and receipts. Only the mismatches reach a person.
- Approvals. Discounts, credit holds and purchase requests go to the right person with the facts attached, and the answer is recorded.
- Reporting. The weekly numbers are put together and sent, and nobody exports anything.
Code or no-code
We write automations as code: scripts and small services that run on your rules. Code can be tested, kept under version control and read by the next developer.
No-code tools such as Zapier, Make and Power Automate suit small, low-risk hand-offs, and we use them there.
Anything that has to be exact, such as pricing, tax, inventory and accounting entries, always runs on code against your own data.
What you end up with
Each automation keeps a log of what it did and sends an alert when it can't finish. Its rules are written down, so the process no longer depends on one person knowing how it works.
Custom software
When no package fits, we build the internal tool, customer portal or application to fit how your business already runs and the systems it runs on.
Example A customer asks where their order is
- by handThe customer calls or emails their rep.
- by handThe rep looks up the order in the ERP.
- by handThe rep phones the warehouse for the pick status.
- by handThe rep looks up the tracking number.
- by handThe rep calls the customer back.
- automaticThe customer logs in and opens the order.
- automaticThe status and the tracking number are read live from the ERP.
- automaticThey download the invoice themselves.
Steps done by hand: 5 today, 0 after.
What we build
- Internal tools. Order desks, quoting tools, scheduling boards and pricing calculators.
- Customer and vendor portals. Order status, reorders, documents and invoices, read live from your ERP.
- Dashboards. One screen with the numbers from several systems.
- Spreadsheet replacements. A proper application for the workbook the business has outgrown.
- Floor and field apps. Software for the warehouse or the road, on tablets and phones.
When custom is the right call
Buy a package when one fits. Custom software is worth the cost when your pricing, your approvals or your process is the reason customers pick you, and every package would make you change it.
It also makes sense when your people spend hours each week working around a tool.
How we keep it maintainable
We start with the smallest version that does the real job, and extra features wait until it is in daily use.
We use common, well-supported technology such as Postgres, TypeScript and Python. You own the code and the data. The software ships with documentation and automated tests.
Websites and e-commerce
- B2B stores. Each customer sees their own pricing and terms, taken from the ERP.
- Shopify and BigCommerce stores. Inventory and orders stay in step with the back office.
- Product catalogs. Pages that update from your ERP when a product or price changes.
- Company websites. Fast pages that make it clear what you sell and how to buy it.
We take on web projects where the site is part of a bigger system, and the store is one more system that has to agree with the ERP. If you only need a brochure site, a web design studio will serve you well, and we'll tell you so.
How we work
Discover
We sit with the people who do the work and map how orders, quotes and data move today. You get a written scope and a fixed price.
Architect
We decide what connects to what, where the data lives and what happens when something fails, and we write it down.
Build
We build in short rounds, and you see working software at the end of each one.
Deploy
The new system runs beside the old one first. We switch over once the numbers match.
Support
We monitor it, fix what breaks and change it as your business changes.
We write code against APIs and databases, so the same input gives the same result every time. More on our approach
We connect to whatever you already run.
These are examples, and the list doesn't stop here. If your software has an API, a database or a file export, we can build to it. Every job is a custom fit.
- NetSuite
- QuickBooks
- Epicor Prophet 21
- SAP Business One
- Acumatica
- Infor
- HubSpot
- Salesforce
- Zoho
- Shopify
- BigCommerce
- Amazon
- Stripe
- Postgres
- SQL Server
- Excel
- Google Workspace
- Microsoft 365
- Power Automate
- Twilio
- EDI
- Email inboxes
- Legacy databases
- Your system
Email inboxes to Epicor Prophet 21 to HubSpotAn emailed purchase order is entered in the ERP, and the rep sees it on the account.
Discuss your project
Tell us what is slowing your team down. We reply within one business day and set up a 30-minute call about the problem. References are available on the call.
You can also write to hello@gifsolutions.io.