Kirk & Co., home Start a conversation

Custom operating software for teams outgrowing spreadsheets

Turn the work between your tools into one clear system.

Kirk & Co. replaces the spreadsheets, inboxes and memory holding your operation together with software built around how your team actually works.

Tell us where work gets stuck See how it connects

Elijah Kirk, founder. You work with the person who designs, builds and supports your system, in Vincennes, Indiana.

One job, kept in six places. Sample data. The drawing shows one water heater job scattered across an inbox, a jobs spreadsheet, a crew calendar, an accounting tool, a text message and a sticky note. The copies disagree on the customer’s name and the day of the visit.

One request, followed through

Watch one job go from six places to one record.

A water heater replacement, from the first email to the paid invoice: first the way most teams handle it today, then the way a tailored system does.

  1. 01An inquiry arrives

    Maria Alvarez emails about a leaking water heater. It lands in one person’s inbox, and only that person knows it is there.

  2. 02It is copied by hand

    Her name, address and the job are typed again into the jobs spreadsheet, the crew calendar and the accounting tool.

  3. 03The copies drift apart

    One copy says Tuesday, another says Wednesday. One spells her name Alverez. Nobody can tell which is right.

  4. 04The records connect

    In a tailored system the inquiry becomes one record. The schedule, the job and the invoice are parts of it, not copies of it.

  5. 05Everyone sees the same job

    The office, the crew lead and the owner open the same record and get the same answer: Tuesday, 8:00 AM, Crew 2.

  6. 06The numbers keep themselves

    When the invoice is paid, the month’s figures update from the record. Nobody rebuilds a spreadsheet to find out.

Sample data. An illustration of a tailored system, not a screen from a product.

What you can check

What stands behind the work

Explore the products Kirk & Co. operates, the websites it has built, and the person responsible for your project.

  • Product

    Kirk & Co. built the CRM it runs on

    Horizline began as the system Kirk & Co. built to run its own client work. It is now offered to contractors and service businesses on two published plans.

    About Horizline

  • Web application

    A live dataset players use

    The Arcane Odyssey Hub’s item database lists 1,708 entries, beside a character builder and tier lists marked with their game patch.

    arcane-odyssey.com

  • Websites

    Four Indiana businesses

    Kirk Web Design, the company’s website division, built the sites for Aureboros Photography, Grundman Shoe, R.A.D. Construction and Pea-Fections.

    See the work

  • Founder-led

    One accountable builder

    You work directly with Elijah Kirk, who designs, builds and supports your software from Vincennes, Indiana.

    About the company

Selected work

Two systems, told from the problem up

What was broken, what was built and what changed. The full case studies show the screens and the decisions behind them.

Case study 01 · Kirk & Co., in-house

From scattered client work to the CRM Kirk & Co. now offers

Problem
Running Kirk Web Design, client records, inquiries, invoicing and follow-up sat in too many places to give one view of the work.
Built
One record per customer from the first call to the paid invoice: leads, quotes, jobs with their tasks and crew, and payments from Stripe.
Changed
The system became Horizline, which Kirk & Co. now offers to contractors and service businesses.
Read the Horizline case study
Horizline’s Overview: payments received, the amount outstanding, the open pipeline and open jobs, above a list of what needs attention.
  1. 1Payments received and outstanding, from the business’s own Stripe account.
  2. 2The open pipeline and open jobs, counted from the records.
  3. 3What is overdue or waiting on someone, in one list.
Horizline’s Overview, with sample data.

Case study 02 · Web application

A fast-changing game, made searchable

Problem
Players arrive with one specific question, and community wikis go stale between game patches.
Built
Entry points by what a player wants to do, a character builder that resolves stats into a build, a searchable item database, and tier lists marked with their patch.

1,708item entries in one searchable database, November 2026

Read the Arcane Odyssey Hub case study
The Arcane Odyssey Hub character builder: a level slider and stat sliders on the left, and the detected build, Mage, with its strengths and weaknesses on the right.
The Arcane Odyssey Hub item catalogue, headed 1,708 wiki entries, with counts for weapons, tools, armor, accessories, ship parts, relics and items.
The character builder and the item database, as published.

Websites for Indiana businesses, through Kirk Web Design

See all the work
  • The Aureboros Photography homepage.

    Aureboros Photography

    Product photography studio

  • The Grundman Shoes homepage.

    Grundman Shoe

    Footwear retailer

  • The R.A.D. Construction homepage.

    R.A.D. Construction

    Construction company

  • The Pea-Fections homepage.

    Pea-Fections

    Bakery and restaurant

Where it hurts

Which of these sounds like your week?

Choose the one that costs you the most time. Each opens the kind of system that usually fixes it, what it replaces, and where you can see one working.

01

We re-enter the same information in multiple places.
Likely system
A shared customer and job record
What it replaces
Typing a customer’s name, address and job into the quote, the schedule and the invoice separately, then fixing the copies when they disagree.
What it could include
  • One record per customer, entered once
  • Quotes, jobs and invoices that read from it
  • Imports from the spreadsheets you keep now

Working example

Horizline keeps one record from the first call to the paid invoice. Converting a lead copies its details to the new client and links the two.

Read the Horizline case study

Tell us where you retype things

02

Nobody can see the current job status.
Likely system
A job board everyone reads from
What it replaces
The whiteboard, the “where are we on this?” text thread, and the one person who always has to be asked.
What it could include
  • Stages, owners and due dates on every job
  • Views for the office, the crew and the owner
  • What is waiting, and on whom

Working example

Horizline’s Jobs list shows every job, who runs it, how many of its tasks are done and what it is worth.

See the screens

Tell us how you track jobs today

03

Our process lives in one employee’s head.
Likely system
Workflow software with your steps written in
What it replaces
Steps that depend on memory, approvals by text message, and the week nobody can cover when that person is out.
What it could include
  • Steps and hand-offs in the order your team works
  • Rules for approvals and exceptions
  • A record of who did what, and when

Working example

In Horizline each business names and orders its own pipeline stages, and the activity log shows who changed what.

About Horizline

Walk us through the process

04

Our tools do not communicate.
Likely system
Connections between the tools you keep
What it replaces
Copying the same details from one tool into another by hand, and checking later that both still match.
What it could include
  • Links to accounting, payment, email and calendar tools that allow them
  • Records created from your web forms
  • Reminders tied to real events

Working example

Horizline connects to a business’s own Stripe account, and each client’s invoices are filed against that client.

About Horizline

List the tools you use

05

Basic reporting requires rebuilding a spreadsheet.
Likely system
A dashboard drawn from the records
What it replaces
Monday-morning spreadsheet assembly, and totals that change depending on who ran them.
What it could include
  • The few numbers that drive your decisions
  • Filters by crew, service, customer or period
  • A path from each total to the jobs behind it

Working example

Horizline’s Overview shows payments received, the amount outstanding, the open pipeline and open jobs, straight from the records.

Read the Horizline case study

Tell us which numbers you need

06

Customers or field staff keep calling the office for updates.
Likely system
Sign-ins for your crew and your customers
What it replaces
Status phone calls, schedules sent by text the night before, and documents passed around as attachments.
What it could include
  • Staff who see the work assigned to them
  • Status, documents and messages for each job
  • Pages that work in a phone’s browser

Working example

In Horizline each team member has their own sign-in with the access you choose, and contacts, the pipeline and jobs fit a phone’s screen.

About Horizline

Tell us who keeps calling

How a project runs

Understand the work first. Then build the system.

Each phase ends with something you can hold. The examples under each one use sample data.

  1. Phase 01

    Understand

    Talk with the people who do the work—the office, the field, the owner—and trace how a job actually moves: where requests arrive, what gets typed twice, where things wait.

    Discovery notesSample
    • Requests: phone, web form, texts to the owner
    • Quote typed in a document, then retyped for the invoice
    • Crew learns the schedule by text the night before
    • Name and address typed 3 times

    You getA plain account of how work moves today, and where it breaks down.

  2. Phase 02

    Map

    Draw the system before building it: the records you keep, the stages work passes through, who needs to see what, and which steps should happen on their own.

    Data model and flowSample

    Customername, address

    Jobvisit, crew

    Invoiceamount, status

    InquiryQuoteApproveScheduleInvoice

    You getAn operations map and a defined first release you can review.

  3. Phase 03

    Build

    Design and develop in working increments, using your real terms and sample records, so you review usable software early rather than a long document.

    Release 0.3, for reviewSample

    Job J-207Scheduled

    CustomerMaria Alvarez

    VisitTue · 8:00 AM

    InvoiceDraft

    You getWorking software set up for your team, with existing records brought in where they can be.

  4. Phase 04

    Evolve

    Stay with it after launch: fix what gets in the way, adjust as the business changes, and add the next piece when it earns its place.

    After launchSample

    1.1Crew view shows the parts list

    1.2Owner report by service type

    1.3Reminder the day before each visit

    You getDirect support from Kirk & Co., the company that built it.

Questions before you write

Do we have to replace the tools we already use?

No. A system can connect to the accounting, payment, email and calendar tools that allow it, and bring in the spreadsheets you keep now. Often the tools are fine and the work between them is what needs fixing.

What do we get before anything is built?

A plain account of how work moves today, then an operations map and a defined first release you can review.

How soon do we see working software?

Early. It is built in working increments with your real terms and sample records, so you review usable software rather than a long document.

Who supports it after launch?

Kirk & Co., directly. The person who built it fixes what gets in the way and adjusts it as the business changes.

Is there a ready-made option?

If your work fits a CRM for contractors and service businesses, Horizline may be enough. It is Kirk & Co.’s own product, with a seven-day trial.

About Horizline

Horizline

Kirk & Co.’s own product

Horizline, the CRM Kirk & Co. built, runs and supports

For contractors and service businesses that want a ready-made system: leads, quotes, jobs and payments in one workspace the office and crew share.

  • LeadsCalls and web inquiries become leads, with the customer’s details and what they need.
  • QuotesRecord the quote on the lead and move it through stages you name.
  • JobsConvert a won lead to a client and open a job with its tasks, materials and crew.
  • PaymentsConnect your own Stripe account and see what is owed, part-paid or paid.
Explore Horizline Start a trial

Seven-day trial. Stripe Checkout asks for a card and charges nothing when the trial starts.

The Horizline pipeline: stage tabs for New inquiry, Contacted, Site visit and Quote sent with each stage's count and value, and a card for each lead.
The same pipeline on a phone: stage tabs with counts and values, and the first lead card.
Horizline’s own screens, with sample data.
Elijah Kirk, founder of Kirk & Co., smiling, in a blue patterned shirt.
Elijah Kirk, Founder & Lead Developer

Who you work with

You talk to the person who builds it.

Kirk & Co. L.L.C. is independently owned and operated by Elijah Kirk in Vincennes, Indiana. Your first conversation, design decisions and ongoing support stay with the person building your system.

  • Nothing is lost in a hand-off.The person who hears how your work moves is the person who designs and writes the software.
  • Questions get direct answers.You ask the builder, not a coordinator who has to go and find out.
  • Support comes from the source.After launch, fixes and changes come from the person who knows the system best.

“I believe every business or nonprofit is different. Each has different wants and needs that you need to be able to work around. I try to capture that as best as possible in my work and how I run my businesses.”

Elijah Kirk, Founder

About Kirk & Co.

Start here

Tell us where work gets stuck.

The first step is a short message. You don’t need a specification, a budget or the right words for what you need.

Start a conversation

  1. What to send

    A few sentences: what your team does, where work gets duplicated, delayed or lost, and the tools you use now.

  2. What happens next

    Elijah Kirk reads it and replies within one business day with a useful next step. Writing in commits you to nothing.

  3. Rather talk first?

    Write or call directly.

    kirk@kirk-co.com812-690-1753