Share Sales Information in a Simple Business Process

To catch up with the flow of business for up to "orders" from the "quote".

-To check which quote is under the judgment of 'Orders / Lost' anytime
-To tell necessary and sufficient information automatically to relating sections without any leakage when got orders.

First of all, 'Sharing current information' is prior among varieties of affairs in Sales section. In the following Workflow definition, the project management of sales team is defined in a very simple Workflow. It exactly is a Simple SFA. I want to note here is, the daily business report can not be continued if it's not simple.

This Workflow begins with [1. Project Opening report] by a sales personnel. Right after the registration of Project Opening, a Task of [1a. Advice/ Strategy] is allocated to the Sales leader clearly.

[Sales-Quote/Orders share flow]

After that, the sales personnel adds progress when the status changes in his project such as submitting quote or visiting, onto Discussion type data at Task [2. Quote Submitting/ Visiting], then [save]. If there is something should be shared, check the 'In negotiation' flag then [Finish]. In that case, a 'Project progress share email' is automatically sent to members of the team.

In addition, when orders or Lost became final and conclusive, the sales personnel click to select [Status] flag, then 'Finish' task of[2. Quote Submitting/ Visiting]. Doing this, a "I got the Order! email" is sent to members of the team automatically.
(Only the supervisor should know data for analysis on Lost. That is, it's better to be set that 'Case lost email' be sent only to the Leader.)

Unmanned Workflow Starts with Receiving Claim Data

There are Workflows which end a series of processes with totally 'unmanned'.

"Unmanned Workflow", it is a Workflow that only when an error occurs human takes part in it. For example, a Workflow that (1) Accepting requests for "Free Account" on the Web site, and (2) Setting new accounts in the system automatically, then (3) Sending a 'Welcome mail' to the applicant. That is one of 'unmanned Workflow'.

The following is an unmanned Workflow that takes a role of 'Database', receiving sales data from various business processes. Only sales data out of all Claim flow is sent, and sales data of all business is aggregated.

[Unmanned Sales Data flow]

Ease the Monthly Billing

Can you define a 'Workflow'?
Somehow, it often seems "IT knowledge" to be required, but it isn't. Rather, "Business knowledge" is indispensable.

'Billing flow', for example. It is exactly what the core operation, and it's not easy to list up all the processing steps.
1. Complement the series of procedures from 'Delivery / Shipment' of merchandise??
2. Complement the series of procedures from 'Order Report' by salesperson?
3. Complement the series of procedures from 'Query / Leads' ?
It is a hassle just to set 'Workflow range considering to be easy its operation'. And of course, the 'Workflow To Be' depends on the Business line, the organizational size, or organizational culture.

In this article, we would like to take a look at a Billing flow for Cloud services business and Rental business, etc. It is also assumed monthly repeat cases on a contract basis.

[Billing flow - Cloud service]

Flurry of Advices about Proposal Workflow on In-House SNS Feature

"Proposal" is important in business for corporation.

In reality, although there is only way for those proposals 'To be created at the discretion of each individual salesperson', but their Sales executive must always worry that "I suspect if they present sloppy proposals..." But possibly, there might be a guy who is making 'a once in a lifetime proposal' at this moment. (It's the communication that counts!)

In anyhow, we would like to visualize 'the progress of creating proposal' for re-usability of it, and want to develop an environment conducive to give and to receive advices from colleagues. Here, we try to implement a business rule of "Get reviewed by at least one person before submit!" with Workflow.

[Proposal and Review flow(Taskfeed) ]

"Organization" and "Role", Important to Decision Making Workflow

A concept of "Group", which is employed in many system such as Os including UNIX / Linux, or directory services as well as business system. In recent years, Google Apps become having two concepts, "Organization" and "Group".

"Organization" is to manage a company's organizational structure in a tree structure. "Sales" "Marketing Department", "Corporate Planning Department"... To each belonging member is configured. That configuration is not set so often except Move or organizational change. In other hand, for "Group" can be set variety of coordination, regardless of the organization structure. "Football club", "Board of Directors" "General Manager (s approvable of 500,000 yen)," etc.

Now, we call it "Role" on a group which can be set without regard to organizational structure in Questetra BPM Suite. (Ver 8.3 or later) Let's see how a Decision making Workflow is defined with both of "organizational structure" and "Role approval authority".

[Decision Making flow(Org. Role)]

Visualizing "Change of Number of Stock" of Revenue Stamps in Graph

Basic of consumables management is "purchase approval process" and "using process".
If the Workflow management advances, in addition to the above, "conversion process" you may be tempted to manage as well.

However, when you manage each of them in different processes, so-called "number of stock" will not be recognized. In this article, we would like to think about "supplies purchasing and using applications" which integrates the entire process of "supplies management system". Of course, the quantity of the item become "-1" at the time "using application".

In this way, "the latest log" and "change of stock graph" will be able to be verified any time with Excel download or Google Spread Sheet button. (wonderful!)

Note that if you expand the range of consumable items too much from the beginning, the whole work will not go well. How about starting with 'postage stamps' and 'revenue stamps'?

[Stamp application]

Legal Registration for Private Placement

In Japan, there are qualifications to act for "Legal Procedure"

• Certified Tax Accountant for 'Tax office'
• Shiho-shoshi Lawyer for 'Legal Affairs Bureau / Court'
• Gyosei-shoshi Lawyer for 'Government office'
• Patent Attorney for 'Patent Office'

That means for a company, must choose to ask those agencies, or to do by themselves on the "Legal Procedure". In either case, it has to be exactly recorded as a company Operation.

Introduce a Workflow and leave exact record of Operations. Not only leaving the deliverables of Capital proceedings, you'd better to try to share realtime progress of Legal Registration.

Here, we introduce a Workflow for "Capital Increase" (Capital proceedings). The final document which created at the end of the Workflow is "Application for Corporation Alteration Registration" for 'Bureau of Legal Affairs', but it is a long way to get there...

[Capital proceedings - Stockholders' Meeting]