Taxidermy Software

Taxidermy software for mounts that take months, not days.

A mount moves slowly: freezer, tannery, form, bench, drying wall, pickup. We turn that long chain into one system where every specimen has a tag, a stage, and a balance your customer can check without calling.

See our work

Bring one stuck workflow. Leave with a build, buy, repair, or wait recommendation.

Trusted by

Perceptional logoMusgrave GroupUrShipper logoBrux Dental SolutionsBella Skin Institute LogoEnergia RewardsDraftly logoTuneClub LogoSekou LMS logoLogo of food order management app gulaSnelwegDealsGrubly logoPSi logoInstantor Rewards logologo of Mobile app for events, membership clubs, and communitiesAldiFest retail campaign logoVidmattic logoEMS Connect logoWorx Squad logologo of Online Web App For Making Intrologo of Referral and Viral Marketing PlatformConcurrences logoGE logoTicketstop logo

The brief

Start with what is not working.

Good software decisions begin with the constraint, not a list of features or a preferred technology.

01

The customer calls again to ask where their mount is, and the answer is in someone's head.

02

A cape comes back from the tannery and nobody can say which customer it belongs to.

03

The deposit was taken in the fall. The balance, the form cost, and the tannery bill live in three different places.

Plain answer

Taxidermy software tracks one mount from freezer intake to pickup: the specimen tag, the species and pose record, the tannery shipment, the deposit and the balance still owed, and the stage the customer can check without calling. Custom software fits when paper tags and memory can no longer carry a pipeline that runs for months.

What to remember

  • Give every specimen one tag and one record at intake, so a cape, a set of antlers, and a skull never part company with the customer who owns them.
  • Track the tannery as a stage of its own, with what was sent, when it went, and when it came back, tied to the mount it belongs to.
  • Hold the deposit as work still owed, and keep the balance, the form cost, and the tannery bill on the same record as the mount.
  • Let customers check their own mount status, so the phone stops carrying the same question all season.
  • Order the form when the deposit lands, not when the bench is ready, so a finished cape never waits weeks for parts.

Fit

Custom software should carry a mount for months, not just a day.

A feature request is not enough. The case is real when the same problems show up at intake, at the tannery, and on the phone.

A fit

Specimens arrive in a short season and finish across the next one, while their status lives on paper tags and in memory.

Customers call through the wait to ask where their mount is, and the honest answer takes time to piece together.

Deposits, tannery bills, and form costs for one mount sit in different places, so the balance at pickup is worked out by hand.

Not a fit

A maintained product already handles your intake, stages, and customer updates with reasonable setup.

Your stages and prices are still changing every month, so software would freeze a moving target.

The brief is a feature list with no named owner for the workflow it is meant to fix.

Not sure which side you are on? Use the first call to make that decision. A useful answer may be to buy, connect, repair, or wait.

The mount leaves. The questions start.

A taxidermy job does not move like other work. A hunter drops off a cape in the fall, it waits in the freezer, the hide ships to a tannery and stays away for months, and the finished mount goes home the following summer. For most of that time nothing is visibly happening, which is exactly when the customer calls. Where is my mount? The truthful answer is spread across a freezer tag, a tannery shipment list, and the memory of whoever skinned it.

The same looseness shows up in the money. The deposit was taken at drop-off and feels like income, but it is really work still owed. The tannery bill for that hide lands months before the mount earns anything. The form gets ordered late, so a cape that is ready waits at the bench for parts. None of these facts live together, so nobody can see the whole pipeline, or what it is worth, in one place.

Underneath both problems sits one missing record. Every specimen needs a single home: who owns it, what it is, which pose was agreed, where it physically is, which stage comes next, and what is still owed on it. Studios that run a shorter queue face the same shape of problem; see how pottery studio management handles work that waits its turn, stretched here across seasons instead of weeks.

Custom software earns its place when one system carries a mount from intake to pickup with that record attached the whole way. The first release should complete that one path. It should not try to replace every tool you own at once.

Where the long wait leaks time.

The screen is only one part of the job. The real scope is the intake record, the tannery round trip, the stages in between, what the customer can see, and how the balance is settled at pickup.

Intake that finishes the record

Customer, species, what was dropped off, licence and tag numbers, agreed pose, reference photos, price, deposit, and freezer location, all captured while the specimen is still at the counter. Nothing is left to be reconstructed from a paper tag in three months.

A tag that follows the specimen

One tag and one record per specimen, whether it sits in your freezer, rides in a tannery batch, waits on the bench, or hangs drying. When a cape and antlers take different paths through the shop, both stay tied to the same customer and the same job.

Tannery shipments with a return date

Hides ship in batches with the tannery, the date, and the mounts in the batch written down. Returns are matched back to their mounts, and a hide that stays away too long shows as overdue on the board instead of surfacing when a customer asks.

Status the customer can check

Each mount carries a stage a customer can open on their phone: received, at the tannery, back and waiting, on the bench, drying, ready for pickup. The stage changes as the work moves, so the routine calls drop away and the phone is free for new work.

Deposits and balances on the mount

Agreed price, deposit, part payments, form cost, and tannery bill sit on the mount record itself. The balance at pickup is already known, and the owner can see deposits held as work still owed across the whole pipeline. The pattern is the same one custom software development applies to any long job: money follows the work, not the calendar.

Which one is yours?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

One pipeline, several trades

Deer in the fall. Birds, fish, and full body work all year.

Most studios run more than one kind of work through the same freezers and the same bench. Each line needs its own stages, and one system has to hold them all without mixing them up.

Game heads and shoulder mounts

The seasonal surge line: heavy intake over a few weeks, capes out to the tannery in batches, forms ordered as deposits land, and a long bench queue worked in drop-off order. The board shows which month of intake is on the bench now, so a turnaround answer is a fact, not a guess.

Birds, fish, and full body work

Smaller lines with different stages and different hands: birds that never leave the building, fish with their own drying and painting steps, full body work that ties up the bench for weeks. Each line keeps its own stage list inside the same record, so a customer question is answered the same way whatever the species.

The studio view across every line

One board shows what is in the freezer, what is away at tanneries, what is on the bench, what is drying, and what is ready for pickup, with the deposits held against all of it. Owners see the whole operation without asking for a report. Wider field service and home services work follows the same rule: one record, carried end to end.

Proof

The fifth attempt became a product customers could keep using.

UrShipper had already worked with four development vendors. Its founder describes the communication and decisions during the recovery.

The case study documents a 14-week recovery, five carrier connections, a Shopify fulfilment workflow, and client-reported results. It is one comparable project, not a promise that every inherited codebase can follow the same plan.

Read the UrShipper case study

Which part of the pipeline is costing you the most right now?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

How it works

Close one expensive risk before opening the next.

Each stage answers a buyer question and leaves behind a decision you can inspect. The next stage only opens when the expensive uncertainty in the current one is small enough to accept.

  1. 01
    Understand

    Trace one full mount

    Where does a mount actually lose time or go missing?

    Follow one deer from the counter to the wall. Include the intake rush, the wait in the freezer, the tannery round trip, the late form order, the drying time, and every customer call in between.

    Decision produced

    A map of one mount from drop-off to pickup, with the freezer, tannery, bench, and drying stages, the exceptions, and the money at each step written down.

    Risk closed

    Paying to automate the visible symptom while the expensive constraint remains.
  2. 02
    Shape

    Choose the first useful release

    What needs to exist together for one useful result to work?

    Choose the shape from the way the work happens: a counter screen for intake, phones or a workshop screen for stage changes, and a simple page customers open to check a mount. Name who can see and change what, the exceptions, and what done looks like for the first path.

    Decision produced

    The first path, usually intake to tannery to customer status, with the specimen record, the stage list, and the deposit record it cannot work without.

    Risk closed

    A small-looking feature list that quietly depends on several screens, systems, and owners.
  3. 03
    Prove

    Review working software

    Will it hold up in the fall rush, not a tidy demo?

    Review the product against the agreed workflow. Take in a deer with a licence number and a deposit. Ship a batch of hides and match them back. Move a mount to drying and watch what the customer sees. Then settle a pickup balance.

    Decision produced

    Working checkpoints tested with a real intake day, a tannery batch going out and coming back, a pose change mid-job, and a pickup with a part-paid balance.

    Risk closed

    Discovering the important gaps after the freezers depend on the release.
  4. 04
    Transfer

    Release, measure, and hand over

    Did the new path improve the original constraint, and can another capable team operate it?

    Start with one intake season or one species line. Compare status calls, lost track of specimens, and time spent settling balances with the starting point before adding the next workflow. The wider method sits behind custom software development.

    Decision produced

    A controlled release, a comparison with the starting point, operating notes, an account ownership map, and a recommendation for what should happen next.

    Risk closed

    Measuring activity instead of the business result, or depending on the original vendor to keep the system running.

What it costs

Every project starts at $10000.

The first phase turns the costliest patched workflow into a scoped build with written acceptance criteria.

Starting investment

Starts at $10000

Workflow complexity, systems to connect, data migration, and user roles set the scope. After a 30-minute call, you get a written build, buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.

Work with us

Bring one stuck workflow. Leave with a decision.

In a 30-minute call, we will help you decide whether to buy, connect, repair, build, or wait. If custom software is not the sensible next move, that is still a useful answer.

  • One named workflow owner and one complete path for the first phase.
  • Scope, price, what 'done' looks like, and exclusions agreed before paid work starts.
  • Code, cloud, data, and provider access remain under your control.
  • Post-launch warranty cover for defects in the agreed scope.

Common questions

It is the system that carries one mount from the day a specimen arrives to the day the customer collects it: the intake record, the freezer location, the tannery shipment, the mounting stages, the deposit and balance, and the pickup. For a taxidermy studio that means every specimen keeps its tag, its owner, its agreed pose, and its money in one record for the whole journey, which can run across seasons.

Give the customer a status they can check themselves. When a mount moves stage, from freezer to tannery, from tannery to bench, from bench to drying, the customer sees the new stage and a plain note about what happens next, by a private link, a code on their receipt, or a simple page they open on their phone. The calls do not vanish, but the routine ones do, because the answer no longer lives only in your head.

The customer and how to reach them, the species, what was actually dropped off (cape, antlers, skull, whole bird or fish), the tag or licence numbers the law asks you to record, the mount and pose agreed, reference photos, the price, the deposit taken, and where in the freezer the specimen went. Intake is the one moment when all of that is in the room at once, so the record should be finished before the specimen leaves the counter.

Each hide is recorded against its mount before it ships: which tannery, which batch, the date it left, and what should come back. When a shipment returns, the returning hides are matched to their mounts and each mount moves to its next stage on its own. A hide that has not come back shows up as overdue instead of being discovered when the customer calls, and a returned cape can never be matched to the wrong customer by memory.

The deposit is money held for work still owed, not a finished sale, and the record should treat it that way. Each mount carries its agreed price, the deposit taken, any part payments, the form cost and the tannery bill spent on that mount, and the balance still owed. At pickup the balance is already worked out, and across the season the owner can see the total value of work in the pipeline instead of mistaking a busy drop-off month for profit.

Yes, if the record is built for it. Reference photos attach to the mount at intake or later, and a pose change is recorded as a dated change against the job, with any price difference agreed before the work moves on. The taxidermist works from the latest agreed version, and there is a clear record of who asked for what, which ends most arguments about what was promised at the counter.

They belong on the intake record, next to the specimen they cover: licence and tag numbers, permit details where your state or province requires them, and the dates they were recorded. The software keeps them findable by customer, by specimen, or by number, so an inspection or a customer dispute is answered from the record instead of from a drawer of paper forms. Your local rules decide what must be kept; the system makes sure it stays attached.

Buy an existing product when it handles your pipeline well enough. Dedicated tools exist: Mount Manager, for example, lists a core plan at 50 dollars per month on its site at the time of writing, covering job tracking, automated customer updates, invoicing, and, on higher plans, tannery tracking (confirm current pricing on the vendor site). Have custom software made when your way of working is the part it cannot copy: your own stages, several species lines with different routes, a tannery round trip that parks work for months, or a customer status view shaped around how your clients actually ask. If your stages are still changing every month, settle them first.

The first paid phase may cover a bounded audit, a small working proof, or a first release that completes one full path, such as intake to tannery to customer status. The final price depends on how many kinds of users it serves, what it connects to, whether paper records need moving over, and whether phones in the workshop are involved. The agreed phase is priced in writing before it starts.

Timing depends on scope. A first release that covers one complete path, for example intake record to tannery tracking to a customer status page, is a smaller engagement than one that also carries payments, accounting, and a full workshop board from day one. The schedule is set once the first path and what done looks like are clear.

You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the workflow agreed at the start: take in a deer, ship a batch of hides, answer a customer from the status page. Progress is reported in plain language: what changed, what is next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads.

You own the code built for you and control where it lives, the cloud accounts, the data, and third party subscriptions. Outside services and open source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.

Yes. Takeover starts with an audit: where the code lives, how your data is organised, what is tested, which outside services it depends on, who can see and change what, and how updates go live. Code that is understandable and fit for the next release stays; only the parts blocking reliable work get replaced.

For one small, well defined task with someone technical managing it, a freelancer is often cheaper. The pattern that goes wrong is a non technical buyer coordinating several freelancers and becoming the project manager, the tester, and the person who finds out the pieces do not fit. An agency earns its fee when the work needs coordination across screens, rules, data, and connections: one accountable party, one phase price, and checkpoints against the whole workflow.