Frequently Asked Questions

“What is custom software?”

“Why is the sky blue?”

“Is custom software right for me?”

“How many developers does it take to screw in a lightbulb?”

We answer all these questions and more on a regular basis. Have a question that isn’t answered here? Email

Custom Software FAQ

What can I expect in the development process?

Since the software we write is custom, things will look differently from client to client. But our process stays generally the same. Here’s what to expect: 

  • Project Plan. Before we start any project, we want to make sure we can communicate the scope of what you’re looking at. So we always start with a in-depth meeting with our team of software engineers and a business analyst. Coming out of this meeting, you’ll have a project plan, with milestones and a high-level estimate of what we expect the project to cost.
  • Discovery. For each phase of your project, you’ll have a Discovery meeting with a business analyst. He/She will ask a ton of questions and sometimes watch how you work. Our goal is to become an expert at how that portion of your business runs.
  • Plan. Once we feel like we have a handle on this portion of the project, we’ll create mock-ups of what we expect the software to look like. We’ll meet with you to make sure we are hitting your expectations. We may be back and forth in this phase several times. It’s important to take the time to get things right here, because changes are MUCH cheaper here than once development starts. Coming out of this phase, you’ll have high-fidelity mockups of what this phase of your project will look like. 
  • Development. Once the mock-ups seem right to both parties, our business analyst will start breaking the functionality into user stories, or small bits of development. Our software engineer teams will start in on actually programming your software. 
  • Testing. When the developer thinks the user story is complete, it goes through internal code review, where other developers look at the code to make sure it is following standards, etc. Then our testing department takes a crack at it, to make sure it works as expected. 
  • Demos. Occasionally, we’ll schedule demos with you to show you how things are coming along. There are points in development when there isn’t much to see (especially at the beginning) and points when there is a lot to show. Demos will help us make sure we are on track to your expectations. Sometimes, we’ll have you try to use the software, so we can see how things flow from a user perspective.
  • Deployment and User Testing. Usually at the end of a phase of the project, we’ll deploy everything out to an environment where you can play with it. We’ll ask you to use it and send feedback to us. You’ll have a set amount of time during which we’ll fix any bugs you find.
  • Communication. Outside of the occasional demo, you’ll get a weekly email with details of what we’ve done that week, along with a burn-down of your EduPoints. Of course, we’re always available for a phone call too. 
  • Repeat. Once we complete a phase, we’ll cycle back to Discovery and run through everything again, until the project is complete.
  • Support. It’s important to realize that your software is a living, breathing organism. It lives out on the internet, which is constantly changing. Tools get upgraded. Your software will need regular support. If you do not plan to put money into supporting the software you just built, we recommend that you not build the software at all, as it will be an exercise of frustration for all involved. It’s important to know that you WILL need to put money into support once your project is finished.
Can you deliver my software on time?

The short answer: Yes. We can deliver your software on time.

How do we do that?

We use a tool called Enable Solutions, which gives us our Daily Layered Accountability (DLA) meetings. DLA is a way of checking in daily with teams to see how on-track we are with projects according to various metrics.

Enable engages every employee and aligns every team on delivering mission-specific outcomes in a culture of accountability and continuous improvement. More practically? Our DLA meetings keep us on track to making sure work is done in an expected timeframe. This is important for all of us, but especially for our Apprentices. Giving them an expectation of when we think work should be done and holding them to it is vital to having them be an essential part of our project teams. 

Want to know more about DLA? Read more here.

What is a Business Analyst (and why do I need one)?

Here’s the thing. Software developers know software. They don’t know business (usually—of course there are exceptions). In general, our developers are writing software that will make your business more efficient. You want a business analyst (BA) involved in your software development process because they know business and understand process.

They say the devil is in the details. But really, the devil is in losing track of the details. And losing track is easy to do. But at EduSource, we believe the essence of your business is in those defining details. Our BAs are tasked with collecting all of those details and keeping track of them. To build effective software, we need to know all about your workflow and how each piece of the process works in the whole. We need to know how you think, and how your employees think. We need to know about your revenue streams, about your decision-making, about how we can save you time, energy, and anxiety while we make your business model as smooth as possible.

The best software integrates seamlessly into your business. Having a BA involved in your project is how we make sure that seamless integration happens.

Meet our Business Analyst, Patric Welch.

What is Agile Contracting?

Since this is a newer term in the industry, here’s what it means to us:

Using an Agile Contracting method, clients use EduPoints to “purchase” a certain amount of functionality completed by a team. Though the vast majority of that work is done by a software developer, others help on the project as needed, including a project manager, a business analyst, an architect, and a quality assurance engineer. 

We break any new features or projects into manageable chunks, which we then breakdown further into User Stories. The number of EduPoints that a certain User Story “costs” depends on its size, which ranges from Youth Small (1 EduPoint) to Large (13 EduPoints). 

We love Agile Contracting because we can form a true partnership with our clients, instead of hounding them about new scope (companies that use a traditional “fixed bid” method have to worry about this). When you want to add something to your project, you just “spend” the appropriate number of EduPoints. And we love that we can avoid the micromanaging that often occurs in “time and materials” contracts. If we feel like we need to bring in an architect, we do so, without haggling about an extra hourly rate. It’s all rolled in. 

Training FAQ

How does an apprenticeship compare with a programming internship?

An apprentice is someone who is learning a trade from a skilled worker. Historically, apprenticeships were a primary method for adult education in America. And they still are in certain industries.

Recently, apprenticeships are making a comeback, especially with the crisis of cost associated with post-secondary education. Why shouldn’t young adults get paid to learn their trade, complementing a formal education? We believe people learn best through doing, so we pair apprentices up with full-time software engineers to get a deep-dive into the world of custom software creation. Our apprentices work full-time for a set period or part-time while also taking classes.

How is this different than a programming internship?

  • Apprenticeships last longer. Truly learning practical skills doesn’t happen in a month or two. It takes time. Our apprentices are encouraged to work for us for up to two full years while they are in school.
  • Apprenticeships are built on mentorship. Most traditional internships will have interns working together to accomplish something that isn’t vital to the company’s success. EduSource apprentices work right with our full-time developers to complete real functionality on real projects. The whole point is to learn from someone who is already doing this professionally, not to experiment in a vacuum.
  • Apprenticeships are focused on education. The point of most internships is just to get students into a professional environment to learn. That’s valuable. But EduSource takes it several steps further. With the intent being to build professional software artisans that can truly contribute to a project, we include things like book clubs, lunch and learns, weekly EduSource U classes, and one-on-one coaching.
What about working with millennials?

Just because the young people in our office wear cargo shorts and flip-flops and can occasionally be seen watching “The Office” with headphones over their lunch hour, don’t assume that they should be treated like “interns.” We do, actually, have a lot of interns (read more about our two-year apprentice program here) around. But it would be a huge mistake to think that these students are best used by getting coffee or making copies. We choose our apprentices carefully, and boy, are these students impressive. They start writing code by their third day with the company and are some of our most bought-in employees.

We are always on the lookout for “experts” in different areas of technology within the company, and several of these unofficial titles are held by people that have been out of school for 1-2 years. Makes no difference to us. Why should it?

Our company’s average age is 28, and we love it! Check out The Truth About Millennials to get the rest of our thoughts.

What is your On-Campus Apprentice Experience?

EduSource is now offering an On-Campus Apprentice Experience to universities. Students work in teams to complete software and data analytics projects under the tutelage of EduSource employees. The experience takes place on campus, with students having specific work hours to meet with their teams. 

Teams are led by a student Team Lead, and Team Leads are mentored by a Program Director. Each student holds a specific role on the team, such as developer, UI/UX, business analyst, quality assurance, etc. These roles meet weekly with an industry coach that teaches them more about how to do their jobs and also weekly with their specific team to measure success. 

Read more about the new On-Campus Apprentice Experience here.

General FAQ

How did EduSource get its start?

That’s a fun story.

Back when Jason had a small company (called jrbeutler, inc.) that consisted of, well, just himself, he was consulting at a local logistics company and overseeing an outsourced team from India. At the same time, he was teaching a computer science class as an adjunct professor at Taylor University.

As the semester wore on, Jason discovered something surprising: the students were writing better, more concise, more maintainable code than the India team. An idea formed: what if we outsourced software-writing to local college students rather than overseas?

From there, the ideas snowballed. What if we brought in a few carefully selected students to work as a part of our development team? What if we hired them for two full years and spent the time training them to program in a real development environment, as a part of a real programming team? Thus, the “EduSource” part of jrbeutler, inc. was launched.

That’s not the end! Check out this blog post to read the rest of our story.

What Are EduSource's Core Values?

At EduSource, we’re anything but mundane. So when we convened our leadership team and tasked them with creating core values, we got some craziness. “Let’s base each one on a movie character.” “Or how about an obscure TV personality?” We got a lot of ideas. We had a lot of debate.

At the end of several meetings, we agreed on one thing: we wanted each core value to have a story. We wanted them to mean nothing to someone who just walked in off the street and everything to our team. We hoped by using core values that told a story, our team would remember them, internalize them, live them. Here they are:

1. Crownless King
Take ownership
Take responsibility
Give grace

2. Phalanx
Protect each other
Protect the team
March as one

3. Figure-it-Out Gene
Be curious
Be fearless
Find solutions

4. Kaizen
Keep improving
Keep changing
Make it better

Strange words, we know, but packed with meaning for our company. Want to learn the stories behind them? Read our Core Values Blog.

What is EduSource's Why?

At EduSource, we imagine a world in which everyone feels empowered to pursue a career in technology, fully supported through mentorship and with an emphasis on software artisanship.

Read more about who we are and what we believe here