The product
Dragones CRM.
One CRM for one industry. Companies, activities, notes, routes and reports, built around the way a service center sells: by grade, by size, by the pound.
Companies, and everyone who works there.
A company here is a customer account, and Individuals are the people who work there. We keep those separate on purpose, because a service center does not only deal with customers. They track mills, processors, competitors, carriers and prospects, relationships that are not in the ERP and in a lot of cases never will be. Your ERP knows who you have invoiced. This also knows who you are trying to sell to. Addresses are validated against Google Places, so you are not working from whatever somebody typed in four years ago.
Revenue, profit, and shipped weight.
Every company carries its own numbers: revenue, profit and shipped weight, forecast against year-to-date against prior years, and the account list ranks on whichever of the three you manage by. Because it tracks tonnage as well as dollars, you can see an account whose spend held up while its weight fell away, and then open the order lines to investigate what changed.
It also keeps a line weight to three decimals, because a single line can weigh less than a pound and rounding it away would show nothing where there is real material. Above 2,000 lbs it reads in tons, if tons is how your shop talks.
Open the order down to the line.
Open an order or a quote and the lines are there: grade, size, quantity, weight, price, and the margin on each line. On a multi-size order the margin rarely lands the same way on every line, and a rep who can see which line carries it walks in knowing what to protect. It syncs with your ERP about every ten minutes, so what they are looking at is current.
Activities, and the account history.
An activity is any interaction with a customer, and the types are yours to define: a face-to-face visit, a phone call, whatever your team actually does. Upcoming activities are the plan; completed ones are the record, which is what makes the history worth anything a year later. The calendar feeds Outlook or Google, so the day shows up where your reps already look instead of somewhere they have to remember to go.
Activity Rules.
Instead of relying on somebody remembering, you describe the situation once and the system watches for it. Trigger on a quote over a certain amount, on an order over a certain amount, on a schedule, or on a period of inactivity. A rule can run across every account or on just one, and the amounts and intervals are yours to set, because a 30-day gap means something different on a stocking account than it does on a project account.
Example rules:
- Send a thank-you on any order of $10,000 or more.
- Visit every customer face to face at least once a year.
- Call any customer with no quote and no order in the last 30 days.
- Call any customer with no order in the last 90 days.
Notes that work like an account knowledge base.
Notes are searchable, pinned, threaded and linked to the quote or order they are about. Require someone to read one and they will be told; reply and the thread stays with the account. If a rep leaves, the notes do not leave with them.
Routes, and the territory map.
A route is built on Google Maps, and a stop can go on it from the road. Draw a radius around an address, or around wherever you are standing, and the map comes back with every account inside it, which is how "who else is near the one appointment I already have" stops being a guess. Optimize the order of the stops before you leave. Email the route to whoever is driving and every stop on it carries a link to Apple Maps, Google Maps or Waze, so nobody is retyping addresses. The territory map honors whatever filters the grid is holding, so a list of everyone within ten miles who has not ordered this quarter is something you can hand to a rep as a day's work. It installs as an app on the phone in the truck and has a dark theme.
Reports and forecasts, exported to Excel.
Custom reports and sales forecasting cover what the grids do not, and both export to Excel.
Permissions, down to the field.
No two companies in this business are organized the same way. There are inside and outside sales desks, call centers, independent reps who should only ever see their own accounts, and an owner who needs to see all of it. Permissions here go page and action level first, then down to the row and the field, so weight, revenue and profit are three separate grants: a rep can see what an account ships and spends while margin stays with management. You set it up around the business you have rather than reorganizing to suit the software. Data is encrypted in transit.
Single tenant, with your own database.
Every environment is single tenant: one customer, one deployment, one database. That comes from how the application is built rather than from a setting somebody turned on for your account. There is no tenant column anywhere in the schema, so there is no shared table for your rows to sit in, and nothing of yours is sitting alongside another company's waiting on a filter to keep the two apart. The only data your environment can reach is yours.
It is also why the same deployment runs anywhere. We host it in Microsoft Azure, or you host it on your own infrastructure, and it moves from on-premise to hosted and back, because an environment is a self-contained unit.
Connects to what you already run.
Direct connectors to the major metal service center ERPs, syncing companies, individuals, quotes and orders, so the sales floor and the office are looking at the same numbers. It also runs perfectly well on its own, so you can start without an integration and connect one later.
See an account, from order detail to next follow-up.
Book a demo and we will open a real account and go through it line by line. Bring one of your own if you want to. You do not need to send us anything first.