Thank you very much for your consultation on a variety of topics.

From consultations where you have a concrete idea of ​​what you want to do, to soft and fluffy conversations, are you talking about your grand dreams?
The content is wide-ranging, and the literacy level of the customers who consult with us varies widely.

We are professionals, so we will do our best once we have decided to do something .

After the system is completed, we communicate closely with the customer to ensure that the system does not become as difficult to use as it was supposed to be, and we approach development by thinking from the perspective of the user who will be using the system, not just an engineer.

Our engineers work hard every day in order to continue to be a ``development team that can do things right'' and not just one of the many development companies out there

a. The contents of this article are also written for internal engineers.

For this purpose, the following three things are important to consider.

Would you like to work together?

The first thing I think about is whether we can talk about it on an equal footing.

We are not a subcontractor . We believe that you are contacting us because you need to develop something, but for some reason you cannot do it yourself.

As professionals, we will discuss with our clients what is necessary to bring the project to fruition, and in return we will be responsible for completing the project. Of course I have that pride.

Let me tell you clearly what we can and cannot do. If we can't talk as equals about how far we can move forward and where we want to land, things won't solidify.

One of us ends up proceeding with a feeling of discomfort or unreasonableness.
Projects that don't go well tend to have of dissonance in communication I place great importance on whether the client is someone I can talk to effectively.

We believe that equality is not only for the customers we work with, but also for the partner companies that sometimes assist us with development

I believe that when it comes to making good products, there is no right or wrong.
In order to create a good product, we believe that it is important that everyone involved in the project be on an equal footing.

Rather than looking at company size or name value, I think it's simply about whether people want to work together or not, and first and foremost, it's about the people.

In recent years, we have had many meetings online, but we would like to meet with you at least once so we can get to know each other better.

I don't work just to collect money.

I will not participate in the money game.

Unless there is a special reason, we generally do not sell our technology cheaply.
Of course, we do not make any more profit than necessary, nor do we steal referral fees without actually doing any development.

If you are choosing based on price alone, please feel free to look elsewhere.

We also take responsibility for development, so we ask companies that work with us to be prepared to pay the necessary amount.

There are very few jobs that we would like to do simply by matching the amount.
As professionals, we also want to take pride I don't think I'll do anything if I get paid.

As our main business is contracted development, we cannot survive unless we receive work requests from our customers.
However, I believe that hiring and training engineers is just as difficult or even more difficult.

I think it is very important for engineers to work with a sense of satisfaction.

Trade-offs between time, money, and man-hours

For example, it takes time to create a quote.

Sometimes I want an estimate by tomorrow or this week. Some people ask me to do this, but to be honest, it's impossible. Accuracy cannot be guaranteed.

In order to realize what the customer has in mind, engineers think about various things, add functions, and provide estimates for man-hours. (I can't do anything appropriate)

I've been in sales for many years, so I think I have a general understanding, but I don't normally find myself in a situation where I need a quote today or tomorrow.

I think they know that they need a quote at least a week in advance.
I don't understand why they didn't consult me ​​at that point. Think about it from the opposite perspective. That's what I always think.

If it is absolutely necessary, we will give you an approximate estimate.
When making a rough estimate, we will use the requirements definition to reconcile the remaining parts at that time.

Once we have a clear idea of ​​the functions that need to be created, we will confirm and agree with each other to ensure that there are no discrepancies in what we want to do, and then we will create another estimate.

If the delivery date and budget are met at this time, there will be no problem, but if the delivery exceeds expectations, it is necessary to consider cutting down on functionality or moving it to the next phase.

Here too, in exchange for giving something away, you need to give something to the customer as well.

Our company does not offer a ``Get everything for the same price! Campaign'' on a regular basis.

Of course, we may be willing to cooperate with strategic projects or clients, even if it is a bit of a stretch, but basically we will trade what we can and cannot do depending on what we prioritize. I think there will be a break

It's easy to say, ``I'll do my best, I'll do whatever it takes.'' But
I think it's worse for both of us if we lift the lid after we start and say, ``I couldn't do it after all.''

What engineers aim for

I've written this in an arrogant way, but I'm not an engineer. It is our engineers who actually make customer requests a reality.

What I have written this time is rather a discussion of my stance as a sales person who protects the engineers within the company.

This is because we believe that if our engineers can do positive work, it will surely lead to good development for our customers.

As someone who is not an engineer, I see them as magicians who can create systems that don't exist in this world yet.

In order to be able to properly formulate customer requests, it is necessary to learn how to use magic correctly.

First of all, it is important the basic technical ability the communication skills to convey it , and the compassion to be able to imagine the other person's position

Sometimes I am able to express my opinion clearly as a professional instead of following the customer's orders.
In order to do so, I believe it is necessary to acquire the knowledge and experience to back it up

We will continue to provide strict guidance from time to time if you are reluctant to put in the effort and choose only the easy option.

We want them to not only be protected, but also to develop the ability to deal with customers as professional engineers.
This is also a trade-off.

the engineers who work at our company to aim to become engineers who can work anywhere.

Rather than being forced to do work, we take responsibility for the services we are involved in and create and develop them together with our customers.

I believe that this is the direction that the engineers of the Beyond Development Department are aiming for, and that they are engineers who can be successful no matter where they work.

I want to create an environment where these magicians can freely and freely demonstrate their abilities.

[Summary] In other words, this is what it means

I've written with a lot of pressure in my writing, but as professionals, the Beyond Development Department is committed to ``manufacturing'' while closely working with our customers.

● Develop a system that can be used in practice.
It doesn't end with development, but after release, we will continue to grow the product together, including brushing up on it.

● We provide an environment where engineers can work in a positive manner, where
they take pride in the services they develop, not just the work they are forced to do, but on the same level as our customers.

If we can establish a solid relationship with you, our services will start to work properly.

result,

● Obtain mutually acceptable compensation.

My idea of ​​``creating and continuing to support together''

This time I wrote it in a very clear manner.
We are a company with this stance, but if you think this is a good idea, we look forward to hearing from you about system development (lol)